flwm: logout calls /usr/bin/exittc even I have /usr/local/bin/exittc

[jls]

 

[jpeters]

/usr/local  must be a link, so that makes sense

[jls]

Sorry?

/usr/local  must be a link, so that makes sense

If I use openbox instead of flwm there are no problems.
When I click logout on the openbox menu /usr/local/bin/exittc shows up, if I delete it, the base exittc is called, this how also flwm should work

[jpeters]

oh..translation or something, sorry.

[jls]

translations

[jpeters]

just tried /usr/local/bin/testit , /usr/bin/testit in flwm and /usr/local/bin overrides.  $PATH has /usr/local first?

Edit: same with /usr/local/bin/exittc, /usr/bin/exittc; /usr/local overrides


Make sure your  permissions are set correctly. 

[roberts]

I think what jls is writing about is:
Menu.C:    execl("/usr/bin/exittc","exittc");
In flwm source.

I typically use full paths so as to avoid needless searching, especially when a Core system is loaded up the command that I want will be last in the search path.

Couldn't a startup script achieve overwriting of those core elements that have a translation?

[jls]

the philosophy behind linux and windows says that we have a search path, and u cannot go against this.
We don't use logout every 5 minutes.
I've tried do override the original programs in /usr/bin with the translated ones, using the startup script, but I failed. I tried mv cp and rsync but nothing, maybe someone could help me.

[^thehatsrule^: spam removed: sorry, it is]

[mikshaw]

I'm in agreement with jls
Not only does it help with translations (I know nothing about them; just going by what I've read here), but it is common practice to have executables in /usr/bin be overridden by same filename in /usr/local/bin.  This gives the admin greater freedom to add and replace commands without disturbing the base system.

As far as I can tell, full paths to executables are typically used only by root (such as during init, before PATH is set), and user commands typically rely on PATH to allow the user to override system commands without needing root permission (such as replacing commands by adding them to a bin directory in $HOME or by using aliases).

[roberts]

What you both fail to acknowledge is that user commands are typically at the end of the search path.
It is a trivial change and I will do so to accomodate the language translation that jls has been providing.

[roberts]

Done.

[jls]

sorry roberts to make u work more then your health permits.
While I was trin' to sleep yesterday, I thought more about my request and I changed my mind, but I was lazy to go back to the pc, also cause I'm injured this days, and now I see it's already late, u've already done the job.
I was thinking that for a more complete translation I should modify the flwm source code translating the default menu and since I'm there I could myself change the line that calls exittc.

[mikshaw]

user commands are typically at the end of the search path.

/etc/skel/.profile:

Code: [Select]

if [ -d "$HOME/.local/bin" ] ; then
PATH=$HOME/.local/bin:$PATH
export PATH
fi
This isn't a very recent version, but if it hasn't changed it looks like user commands are at the start of PATH.  Maybe I misunderstood what you said.

[jls]

I see again executables in the cpanel called with full path

[roberts]

Old habits are sometimes hard to break. Full path is faster than searching several paths, but I know that your language extension requires such. I have removed full paths from cpanel for next cut.