window title text

[coa]

Hi my windows title text is centered is it any way possible to align the text left. can not find any setting for it.
thanks.

[coa]

i found a theme that had window title text aligned left

[Rava]

i found a theme that had window title text aligned left

Mind sharing what DE you use and what theme has the window title text aligned left?

[beny]

hi coa:https://www.fosslinux.com/3041/how-to-m ... uttons-to-

[coa]

yes i dont mind Rava

Im using Cinnamon Desktop

and here is theme with windows title align left, theme is called mint
https://forums.linuxmint.com/download/f ... c488b3766d

[Rava]

and here is theme with windows title align left, theme is called mint
https://forums.linuxmint.com/download/f ... c488b3766d

Did you incorporate that into your 003- module or did you include it via a personal module (that gets loaded later, e.g. by conveniently giving it a higher number - e.g. 100-cinnamon-patches.xzm ) or via changes= ?

[Ed_P]

(that gets loaded later, e.g. by conveniently giving it a higher number - e.g. 100-cinnamon-patches.xzm )

Not necessary. Alphabetic characters sort after numeric characters, thus cinnamon-patches.xzm works just fine.

[coa]

I just copied the theme to themes folder Rava

edit: and used theme selection feature

[Rava]

I just copied the theme to themes folder Rava

I presume you use the changes= kernel cheatcode then?

[coa]

I used themes selection feature to change the theme

I presume you use the changes= kernel cheatcode then?

no i did not is it good to use?

[Rava]

no i did not is it good to use?

I never use it.
You can create settings/scripts module where you store settings, personal scripts and programs and other additions (best path is in /usr/local/ - e.g. your scripts and programs in /usr/local/bin .
Or when there is a ext[234] partition and your boot medium can symlink to that then you can use $PORTDIR/rootcopy/


I prefer the creation of modules since they work on a backup USB thumbdrive, one as small as 1GB is sufficient for that.

I will soon post my 991-usr_local_bin and 992-rootcopy creation script suite that greatly aids me with that.

[coa]

You can create settings/scripts module where you store settings, personal scripts and programs and other additions

nice did not know that.

[Rava]

nice did not know that.

Since a later loaded module overwrites the settings and files of older loaded modules, I named mine like so:
006-man.xzm (instead of 06-man.xzm, not my module)
985-palemoon-settings--RECENT.xzm
991-usr_local_bin_RECENT.xzm
992-rootcopy_5.0-RECENT.xzm

The files named *RECENT* are symlinks and the real physical file has its creation date in its file name.
I first use a symlink from the boot device (e.g. sda1) to the folder where my modules are, e.g. on sda5 in the folder Porteus_modules/ also to the same filename, e.g. 992-rootcopy_5.0-RECENT.xzm
The reason for that is that I do not need to alter any external boot devices when I use these to load my internal modules, since all first are directed from e.g.
/mnt/sdb1/porteus/base/992-rootcopy_5.0-RECENT.xzm to /mnt/sda5/Porteus_modules/992-rootcopy_5.0-RECENT.xzm
And my make-992-rootcopy.sh script not only creates my 992-rootcopy module but also creates the symlink to its most recent just created version while keeping the older modules as backup.
E.g.:

Code: Select all

root@porteus:/Porteus_modules# ls -o 992-rootcopy_5.0-RECENT.xzm |cut -c 19-
35 2022-12-09 21:13 992-rootcopy_5.0-RECENT.xzm -> 992-rootcopy_5.0_2022-12-09.xzm

You might ask why I do split my settings into two modules, one called 991-usr_local_bin* and one called 992-rootcopy_5.0*.
The reason is: the module 991-usr_local_bin* is meant to have scripts and programs that will work in any DE imaginable. Therefore there is only one recent 991-usr_local_bin* module that will be used by any DE I could possible load.

The module named 992-rootcopy_5.0* is only meant for the current DE. When I use a different DE the contents of 992-rootcopy_5.0* will change accordingly, but most probably not the name (since I am lazy and usually always use the same XFCE version anyway). Unless I switch more often between DEs then I would add the DE name into it, e.g. like so:

Code: Select all

992-rootcopy_5.0-XFCE4.12-RECENT.xzm
992-rootcopy_5.0-XFCE4.16-RECENT.xzm
992-rootcopy_5.0-LXDE-RECENT.xzm

When doing so, I also would move the script suite

Code: Select all

root@porteus:/usr/local/bin# ls -o make-99*
-rwxr--r-- 1 root 2939 2022-11-08 21:30 make-991-usr_local_bin.sh
lrwxrwxrwx 1 root   25 2021-02-27 23:06 make-992-rootcopy.sh -> make-991-usr_local_bin.sh

from 991-usr_local_bin* to 992-rootcopy_5.0* so that every DE will have its own version and settings of these scripts since my script(s) stores its settings internally and not uses parameters or a settings file.
The script is physically only one script, but it looks up if it was started as "make-991-usr_local_bin.sh" or as "make-992-rootcopy.sh" and then acts either in the one way or the other.

[coa]

thanks for all the info i might try it someday
is there a tuturial out there for making settings module?

[Rava]

is there a tuturial out there for making settings module?

I will post my module creation suite soon. I think I have to re-write part of the article, I have written it weeks ago already and PM'd it to someone for review, but since it is a bit of a complex script suite I am not sure if I was able to explain everything in an easy to understand way in the current unpublished version of it.
I can PM it to you if you are willing to look it over? When you see no major flaws in how I wrote the article then I will publish it.