- This topic has 199 replies, 27 voices, and was last updated May 5-3:20 pm by Robin.
-
Posts
-
Dave
@RJP,
You should be able to edit ~/.desktop-session/default-desktop for this. (/etc/skel/.desktop-session/default-desktop)
Also there is the /usr/local/lib/desktop-session/desktop-session-menu-window which should allow you to choose another desktop session.
Also there is the desktop submenu under the main menu for switching the default desktop session. Whichever is chosen is then the default.I think if the default is set in slimski this would break the system to save the users last chosen session but I have not tested to verify.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
PPC
Nice idea – there’s a gui for that: desktop-session-menu-window ignore-settings
Edit: sorry, I forgot to finish the phrase: … and it can easily be placed in Control Centre!
- This reply was modified 1 month, 2 weeks ago by PPC.
@Robin – I noticed that, in fact, none of the changes your workspace manager script perform lasts after restarting icewm but in this particular WM I know how to make the change “stick” check if prefoverride file has any line refering to the number and/or names of the workspace. If none exists, simply write the correct values of the varibales to the prefoveride file. If any value exists, replace that line with the new variable names… I offer assistence to try to implement this, making an already great script (that’s already part of antiX23 beta1) into an almost perfect tool!
Brian Masinick
@Robin – I noticed that, in fact, none of the changes your workspace manager script perform lasts after restarting icewm but in this particular WM I know how to make the change “stick” check if prefoverride file has any line referring to the number and/or names of the workspace. If none exists, simply write the correct values of the variables to the prefoveride file. If any value exists, replace that line with the new variable names… I offer assistance to try to implement this, making an already great script (that’s already part of antiX23 beta1) into an almost perfect tool!
I’m sorry, I noticed the same issue; I probably forgot to mention it. In my case, I’ve updated the files in .icewm for decades now, so I simply updated preferences, replacing the 2 default values with the ones I wanted, restarted and that’s it. @PPC you are also correct that you can use the preferences override file. I’ve never made that a habit; I simply change my entries in preferences since I intend for them to be permanent; either solution works.
Let me know when the change is in place and I will explicitly test it to make sure we have it corrected. Thanks for both of your efforts; these are very useful tools, even to those of us who have edited the files by hand for so many years!
--
Brian MasinickRobin
none of the changes your workspace manager script perform lasts after restarting icewm
Many thanks for the hint, @PPC ! I also noticed this meanwhile. One or two lines of sed -i regex will do the trick. Will see what I can do next days. Please feel free to post any suggestions in case you already have a functioning code line ready.
that’s already part of antiX23 beta1
Great to read. I didn’t even know, since I still need to switch the testing frugal install from alpha to beta as soon I have some spare time for this time consuming task.
Windows is like a submarine. Open a window and serious problems will start.
Brian Masinick
none of the changes your workspace manager script perform lasts after restarting icewm
Many thanks for the hint, @PPC ! I also noticed this meanwhile. One or two lines of sed -i regex will do the trick. Will see what I can do next days. Please feel free to post any suggestions in case you already have a functioning code line ready.
that’s already part of antiX23 beta1
Great to read. I didn’t even know, since I still need to switch the testing frugal install from alpha to beta as soon I have some spare time for this time consuming task.
I’m confident in both of you; thank you for all of your contributions!
--
Brian Masinick
marcelocripe
So as promised, here’s our own antiX Community version of this tool, mean and lean (at least I hope it is, the way I’ve written it). I’ve named it aCMG, which means antiX Community MOC Gui, wherein moc means Music On Console, the name of the underlaying console program already present in antiX.
Robin, I sent a (1) merge request for the .desktop file of your newest program.
As soon as possible, I will send you the “.po” file translated to “pt_BR”. Or if possible, please send me the “.po” file that you used as a reference to create the “.mo” that is in the “.deb” package for me to revise based on your original texts in German. I’m sure the “pt_BR” version will be much better if I compare it with the automatic translation of your texts.
aCMG also deserves to be on Transifex at some opportune time.
Thank you very much for this excellent program.
– – – – –
So as promised, here’s our own antiX Community version of this tool, mean and lean (at least I hope it is, the way I’ve written it). I’ve named it aCMG, which means antiX Community MOC Gui, wherein moc means Music On Console, the name of the underlaying console program already present in antiX.
Robin, eu enviei um (1) pedido de mesclagem para o arquivo .desktop do seu mais novo programa.
Assim que for possível, eu te enviarei o arquivo “.po” traduzido para “pt_BR”. Ou se for possível, por favor, me envie o arquivo “.po” que você utilizou como referência para criar o “.mo” que está no pacote “.deb” para eu fazer a revisão baseado nos seus textos originais em Alemão. Eu tenho certeza que a versão “pt_BR” ficará muito melhor se eu comparar com a tradução automática dos seus textos.
O aCMG também merece estar no Transifex em algum momento oportuno.
Muito obrigado por mais este excelente programa.
olsztyn
ntpsec is a more secure version of ntp.
Should it be turned off by default on live medium?
All logging will be turned off on runit editions.I came to conclusion that chrony is a superior choice for antiX vs. ntpsec, if you need such service at all…
Scenario: antiX 23 Beta. Not running ntpsec runit service as default:
What puzzled me at first was that after recent update (such as yesterday or today) the original memory footprint unexpectedly grew by some 12M, without apparent reason. That indicated to me either a bug in some updated component or unexpected system config change. I identified the culprit, namely the new tzdata, ver 2023c-2. Upgrade of this component entailed start of ntpsec – ntpd daemon, which caused memory footprint to jump by some 12M.
Resolution:
– Either turn off and disable ntpsec runit service
– Or purge completely ntpsec* from the system and install chrony.
In my experience chrony is using just a small fraction of memory footprint (just about 2M) and seems much more efficient, faster and more resilient to network issues in real operation, being more modern design.
Just my opinion…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersXunzi_23
@olstyn, as you posted you have experience with chrony on antiX.
please post full install and secure configuration details on the antiX beta including how you ensured keeping it completely systemd free.
Others can then easily follow your teaching, replicate the install then test the more modern and efficient time synchronization services
while having the smaller memory footprint as you claim.- This reply was modified 4 weeks ago by Xunzi_23.
In my experience chrony is using just a small fraction of memory footprint (just about 2M) and seems much more efficient, faster and more resilient to network issues in real operation, being more modern design.
Just my opinion…Just to expand my obseration:
I am always looking for minimizing memory footprint so antiX 23 can run on minimal hardware. This unwanted jump in memory footprint if ntpd damon is started unexpectedly upon tzdata update is not acceptable. The route I used is the following:
– I purged all ntpsec* from antiX 23
– Updated tzdata to the latest version 2023c-2
– installed chrony. No dependencies were required to be installed. Chrony does not seem to be dependent on systemd/*elogind*
The impact of chronyd on memory footprint measured just 1.7M total according to though ps_mem.py. This is quite minimal compared to ntpd over 12M memory hit. I can put up with this 1.7M toll I think… Chrony operation can be verified through chronyc sources command.
Just my observation…- This reply was modified 4 weeks ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAnother suggestion for improved user experience in zzzFM on future antiX:
Please add these two file handlers to the default antiX zzzFM config. They are meant for handling gpg encrypted files in context menu, since gpg is installed by default on antiX. The entries can simply be added by right click on any file in zzzFM, then „open → file-handler → add”. Not sure to which config file they will go then. Also not sure how this can be prepared for translation.
1.) Decryption
As default for open: checked
Name: Decrypt GPG
MIME Type: application/pgp-encrypted
pathname: *.gpg
command:
if [ -e "$(sed -n 's/^\(..*\).gpg$/\1/p' <<<"%f")" ]; then yad --title="GPG Decryption – Error" --window-icon=dialog-error --image=dialog-error --center --info --borders=10 --text "Error: Target file exists\n$(sed -n 's/^\(..*\).gpg$/\1/p' <<<"%f")" --timeout=5 --no-buttons; exit 0; fi; gpg --output "$(sed -n 's/^\(..*\).gpg$/\1/p' <<<"%f")" --decrypt "%f"; if [ $? -ne 0 ]; then yad --title="GPG Decryption – Error" --window-icon=dialog-error --image=dialog-error --center --info --borders=10 --text "Error: Decryption failed" --timeout=5 --no-buttons; exit 0; fi;
Execute command: checked
In terminal: unchecked2.) Encryption
As default for open: unchecked
Name: Encrypt GPG
pathname: *
command:
if [ -e "%f.gpg" ]; then yad --title="GPG Encryption – Error" --window-icon=dialog-error --image=dialog-error --center --info --borders=10 --text "Error: Target file exists\n%f.gpg" --timeout=5 --no-buttons; exit 0; fi; if [ $(wc -l <<<"$(gpg --list-public-keys | grep ^'pub')") -eq 0 ]; then yad --title="GPG Encryption – Error" --window-icon=dialog-error --image=dialog-error --center --info --borders=10 --text "Error: No GPG keys.\nPlease make sure to import the key\nfor the recipient into gpg." --timeout=5 --no-buttons; exit 0; fi; gpg --output "%f.gpg" --encrypt --recipient $(sed -n 's/^..*\/\(..*\) ..*$/\1/p'<<<"$(yad --title="GPG Encryption" --window-icon=dialog-password --image=dialog-password --no-escape --button=OK:0 --center --form --item-separator='|' --field="Available Keys":CB "$(gpg --list-public-keys --keyid-format long | sed -n 's/^sub \(..*\) \[..*\]$/\1/p' | tr \\n '|' | rev | cut -c 2- | rev)")") "%f"
Execute command: checked
In terminal: uncheckedIf no issues with these handlers show up they might go already into antiX 23 possibly?
Best regards
RobinWindows is like a submarine. Open a window and serious problems will start.
PPC wrote:
none of the changes your workspace manager script perform lasts after restarting icewm
Many thanks for the hint, @PPC ! I also noticed this meanwhile. One or two lines of sed -i regex will do the trick. Will see what I can do next days. Please feel free to post any suggestions in case you already have a functioning code line ready.
I tried to work on this, but unfortunately I can’t find the sources used in antiX 23 beta. Sure, I have my original script code and what I’ve posted here in forum, but I’d rather prefer to clone the antiX repo first for easy and secure handling the merge request later. Unfortunately this won’t work for me by now:
apt-cache show icewm-goodies-antix ... Homepage: https://gitlab.com/antiX-Linux/icewm-goodies-antix ...But this very url returns me a „404 not found” error only:
@anticapitalista : Please let me know the proper URL so I can clone the icewm-goodies-antix package source to fix the antiX-workspace-manager issue PPC has spotted. Many thanks!
Windows is like a submarine. Open a window and serious problems will start.
anticapitalista
@Robin – here it is
https://gitlab.com/antiX-Linux/icewm-goodies
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
blur13
Here is a suggestion, replace nano/vim with micro as the default terminal text editor (even with sudo). Micro is much easier to use since it uses the conventional keyboard shortcuts and generally behaves as expected. Ie ctrl+s saves, ctrl+q quits, etc.
change default sudo editor
sudo update-alternatives --install /usr/bin/editor editor /usr/bin/micro 100- This reply was modified 6 days, 18 hours ago by blur13.
Brian Masinick
I like micro and I have it installed on a few of my systems. It’s neither the lightest nor the most basic editor but it’s definitely easier than vim for a novice to use and more capable than nano.
I think it’s a good idea and a worthy complement to geany, which is a good IDE (Integrated Development Environment) editor. Veteran users will get whatever they want and beginning users are fortunate to be able to type and navigate. If we make any changes a few short HOWTO updates would be great complementary works to explain our new release.
--
Brian Masinick
- You must be logged in to reply to this topic.
