- This topic has 199 replies, 27 voices, and was last updated May 5-3:20 pm by Robin.
-
Posts
-
PPC
@Robin- I just tested your latest script in antiX 23a1- running in pt, running live with the more recent kernel – the list of workspaces still has the reported bug- my solution seems to work fine, as long has the workspace names does not have strange characters like \ / * , etc… So it’s not 100% recomended to use my suggestion…
P.
Robin
@PPC Many thanks for checking! Could you please post/attache the output of
$ icesh listWorkspacestaken when the script fails to display the fields properly? (Please not as screenshot, but either literally copied, within code tag or as attached txt file) Then I can feed the strings to the sed command and see what happens.
I guess there needs to be a more restricted filtering by grep, which by now filters only for #1, #2, #3 … etc. But I can analyze only when seeing the output your system returns. Maybe there exist some major differences on a differently localised system, as your pt_BR instead of my de.
And please post/attach what the script shows on console (There are added some dbugging lines in this version to get some relevant info from running the script)
The cryptic parts displayed in entry fields occur generally only if the command fails to get any string to display. So we need to find out why it behaves on your antiX 23 differently than on mine.
Windows is like a submarine. Open a window and serious problems will start.
@Robin:
The forum mangles the code, so I attached the text…
Edit: I had to compress the text file, duh! š
If I had to guess, the problem is that “workspace” in Portuguese is not one word, but several… but I can’t fight with sed on that, right now…P.
- This reply was modified 2 months, 2 weeks ago by PPC.
- This reply was modified 2 months, 2 weeks ago by PPC.
- This reply was modified 2 months, 2 weeks ago by PPC.
Many thanks, PPC! Now it is clear why the script fails for you: icesh is the culprit.
In your localisation icesh uses different closing quotes than for me. That’s ridiculous! The sting-quoting is meant to stay consistent across all languages. No wonder it fails for you, since my script expects to find the very closing quote than I see here. It is mostly impossible to build something on such an inconsistent basement!
Well, I’ll try my very best to fix that nonsens.Analysis: For you it shows ' (\x27) while my script code searches for ` (\x60) as end marker.
$ echo -n "$(icesh listWorkspaces | grep -F '#0' | rev | cut -c1 | rev)" | hexdump -C 00000000 60 $ echo -n "$(LANG=pt_BR.UTF-8 icesh listWorkspaces | grep -F '#0' | rev | cut -c1 | rev)" | hexdump -C 00000000 27Now, the proper solution would be to run the command without any translation, which means prefixed by
LANG=C icesh listWorkspaces
Unbelievable, icesh doesn’t return anything then. What’s that again? Why?
Same with LANG=POSIX.Will think about how to resolve this properly.
For now: A quick fix. See attachement. @PPC Please check out whether you get better results now.
Windows is like a submarine. Open a window and serious problems will start.
@Robin – yes, scripting can be a messy stuff, with some unexpected results!
On antiX 22: LANG=C icesh listWorkspaces returned “workspace” instead of “Ć”rea de trabalho”- that works, but the ticks before and after the name of the workspace seem to be the same…I’ll try to test the new script later, many thanks for it!
P.
The latest version of the script runs great – please consider contacting the IceWM dev team and ask them to include it (or a even more polished future version of it) by default – this should be an entry in the contextual menu that comes up when users right click the workspace in the toolbar…
I wanted to create a GUI to manage the clock (change 24/12h, hide/show seconds, hide/show different date formats), but Toolbar Icon Manager took a lot out of me… That should also have a GUI to setup- right clicking the clock and changing it does not “stick” after login off…
P.
Brian Masinick
The antiX-workspace-manager does indeed work well. Since I already have 4 workspaces created, and I also have them named, the script recognized this.
I also modified the number of workspaces and I could visually see the changes on the IceWM toolbar; nice work.--
Brian Masinick@Robin – I just looked at the code for antiX-workspace-manager: “LANG=de_DE.UTF-8 icesh listWorkspaces”- Priceless! Smart and efficient way to make icesh behave in a predictable way!
As I said: it was a quick fix, with stress on Ā»quickĀ«, without need of changing the rest of the script code. I’d have preferred “LANG=C icesh listWorkspaces”, since the de_DE is to be considered a pretty unstable method when it’s about long-term. It might break at any time with any updated translation… As you said: On antiX 22 it comes up using LANG=C properly with the desired answer. So the most interesting point is:
Does anybody else see
LANG=C icesh listWorkspaces
not returning anything on antiX 23 (most recently apt-upgraded, and kernel 6.1.10), or does this happen specifically to me only?(while LANG=C icesh -V and LANG=C icesh –help work fine both)
This might be easily a temporary issue only, since we are in an alpha still.
(icesh version on antiX 22 reports 3.1.0, on antiX 23 it reports 3.3.1)Btw, could somebody check whether the column breaking mechanism antiX-workspace-manager script uses in the naming dialog works fine for workspace counts 11, 12, 22, 23 please? The workspaces don’t need to be actually named for this, it is enough to switch back and forth between the count setting dialog and the name changing dialog, using the two buttons āChange Namesā and āBackā while setting different counts.
Windows is like a submarine. Open a window and serious problems will start.
Since I tend to worry about User eXperience, maybe antiX-23 could implement some small changes:
-I’ve been using antiX for years, mostly icewm, and some fluxbox. One thing that annoyed me a tiny bit is the fact that windows that are not maximized tend to pop up in random places. A few days ago I tried to get that fixed, and, as it happens so many times, sharing something here in the forum lead to enlightment. It’s easy, making IceWM always center large windows. In ~/.icewm/preferences, simply include the line:#Always open Large windows on the center of the screen, not in some random place: CenterLarge=1That fixes it for me. Also, if you want to stop small windows (like, for example, galculator) opening in some random place:
#Place small windows below, and to the right, of the previous window title bar: SmartPlacement=0Also, another tiny suggestion, that costs 0 system resources:
Create, by default, the ~/.icewm/themes folder – it’s a tiny help, when users want to use themes they downloaded from somewhere, it saves them the trouble of finding out that the required folder does not exist by default, and having to create it (I know, I know, I want to spoil our users).Edit: IceWM’s tile features are great. I think they should have their own short-cut keys available by default, so maybe include a ~/.icewm/prefoverride file with this contents:
#### KEYBOARD SHORTCUTS TO TILE WINDOWS USING ICEWM'S TILING FEATURES: # Tile windows with the Windows key + arrow keys shortcuts KeyWinTileLeft=Super+Left KeyWinTileRight=Super+Right KeyWinTileTop=Super+Up KeyWinTileBottom=Super+DownEdit2: Now I recall another IceWM related proposal: showing coordinates while dragging a window can be useful, but I bet most people just find it annoying, most of the time, so, set by default, in the preferences file:
ShowMoveSizeStatus=0 # 0/1
PS: I’m aware that, for extermely picky users, it’s nice, having the exact coordinates of the window, so they can select, with pixel point precision, where the windows are.All this proposed changes do make IceWM act in a more “mainstream” way (whatever that may mean, it’s different things for different people), out of the box, and also allow easier access to the tilling features
I’m still trying to find time to create a simple GUI to manage these basic IceWM settings, since using the menu is far from being intuitive.
P.
- This reply was modified 2 months, 2 weeks ago by PPC.
- This reply was modified 2 months, 2 weeks ago by PPC.
- This reply was modified 2 months, 2 weeks ago by PPC.
anticapitalista
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.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
ām still trying to find time to create a simple GUI to manage these basic IceWM settings
That would be really great!
An additional proposal:
There is an annoying behaviour of the default setting present in antiX, when working with text files, you want to copy some string from another window to: While reading you have set the text cursor to the very position you want to insert the additional string. Then you go to another window to fetch the string, which makes hide the original window behind the source window partly. When now clicking to the visible part of the target window to bring it on top, the cursor is set to the point you have clicked by mouse accidentally. That’s kind of stupidity, since this way you have to re-read and look up the precise target position in your text again instead of simply paste the string from clipboard to where the text cursor was positioned before.This can be helped. Set the value “PassFirstClickToClient” in line 37 of the preferences file in your home folder’s .icewm subfolder to 0 (zero), it defaults to 1 (one).
37 # Pass focusing click on client area to client 38 PassFirstClickToClient=0 # 0/1restart icewm. Then it’ll keep the cursor position even when you have to click somewhere into the text area to bring the respective window up to top.
@PPC Would be great if you could add a checkbox for this setting also to your planned GUI, so people can decide themselves how they want it best. I know some people prefer the first click passed to windows, obviously they have not to deal with many opened windows on a small screen, so they can apply the click to upper window border always instead having to click somewhere into the text area.
Windows is like a submarine. Open a window and serious problems will start.
PassFirstClickToClient=0 # 0/1
I tried this. For some reason, on my antiX 22, 64bits, full, runnit, this makes left click on the toolbar’s start menu to stop working (the right click contextual menu still works fine)
P.
Brian Masinick
IceWM has an incredible number of features that can be configured and altered through the configuration files – keys, menu, menu-applications,
personal, preferences, startup, theme, toolbar, winoptions, and you can also have additional variations of menu and toolbar, and probably all of them.I was reading the manual the other day, and though I’ve used IceWM for at least two decades, I’ve probably used only 5-10% of the possible options at the most, and many of them I had no idea that they were available. For such a lightweight window manager it is a lot more capable than most people realize!
--
Brian MasinickXunzi_23
Hallo anticapitalista, ntpsec seems to be working correctly on my system.
My preference.I switched off the NTP and Online checking function in Conmann as well as the
logging start in runit. Conmann now just handles Network connection and DHCP.Sniffed system idle connection IP adresses have all been to router or
NTP servers.OT: Also set desktop session logging level to 5 logs to three.
Would be nice in release as in present setup with 9 the logfiles
do grow rapidly. For those who do not know 5 is error and
fatal logging. 9 Logs everything.- This reply was modified 2 months, 2 weeks ago by Xunzi_23.
- This reply was modified 2 months, 2 weeks ago by Xunzi_23.
- This reply was modified 2 months, 2 weeks ago by Xunzi_23.
- You must be logged in to reply to this topic.
