Hallo,

Current version of Fish is making a little problem: it's changing character
mapping and font without asking the user for opinion first. In the manual
there is a description:

#v+
  On startup, fish evaluates the files /usr/share/fish/config.fish
  (Or /usr/local/fish... if you installed fish in /usr/local),
  /etc/fish/config.fish
#v-


And indeed: in /etc/fish/config.fish there are several verses about this:

#v+
  if status --is-login

        #
        # Set some value for LANG if nothing was set before, and this is a
        # login shell.
        #

        if not set -q LANG >/dev/null
                set -gx LANG en_US.UTF-8
        end

    [ ...more stuff changing mapping and charset... ]

  end
#v-

At the very first line there is a remark: "DO NOT MANUALLY EDIT" - so
actually how, without changing contents of this file, one could set $LANG
variable to disable "set -gx LANG en_US.UTF-8" - when this file is read by
Fish BEFORE the local, user-generated configuration files? And how can
I suppress putting the consoles into Unicode (en_US), which isn't what I want?

Of course, I'm aware, that I can set all this back in my local configuration
files - but does it make any sense to switch local settings twice, instead
of not touching them at all, because the user didn't want it? It's not the
job of the shell to set the character set, font and keyboard mapping,
_unless_ the user _intentionally_ wrote such lines into his local scripts;
it's job of the system boot-up scripts, which has been already done. Why
changing it such senseless way - by testing the existence of the variable,
that obviously couldn't be set _before_ someone logged in?

The fix could be done following way:

1. Current /etc/fish/config.fish should be used as template file, copied
during first execution of fish into user's own  ~/.config/fish/config.fish

2. Every next time - at startup - fish should check for existence of such
local ~/.config/fish/config.fish file - and the global /etc/fish/config.fish
should be read only in case there isn't any local one available.
-- 
regards,
Zbigniew

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users

Reply via email to