Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #235302 > unrolled thread

Re: vim not seeing many Unicode chars

Started byTom Browder <tom.browder@gmail.com>
First post2021-05-18 18:30 +0200
Last post2021-05-18 19:40 +0200
Articles 7 — 6 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: vim not seeing many Unicode chars Tom Browder <tom.browder@gmail.com> - 2021-05-18 18:30 +0200
    Re: vim not seeing many Unicode chars IL Ka <kazakevichilya@gmail.com> - 2021-05-18 18:40 +0200
      Re: vim not seeing many Unicode chars "hdv@gmail" <hdv.jadev@gmail.com> - 2021-05-18 19:10 +0200
        Re: vim not seeing many Unicode chars Eike Lantzsch ZP6CGE <zp6cge@gmx.net> - 2021-05-18 20:40 +0200
          Re: vim not seeing many Unicode chars deloptes <deloptes@gmail.com> - 2021-05-18 21:20 +0200
      Re: vim not seeing many Unicode chars Tom Browder <tom.browder@gmail.com> - 2021-05-20 14:20 +0200
    Re: vim not seeing many Unicode chars Greg Wooledge <greg@wooledge.org> - 2021-05-18 19:40 +0200

#235302 — Re: vim not seeing many Unicode chars

FromTom Browder <tom.browder@gmail.com>
Date2021-05-18 18:30 +0200
SubjectRe: vim not seeing many Unicode chars
Message-ID<CgaLv-5Da-7@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

On Tue, May 18, 2021 at 09:25 Tom Browder <tom.browder@gmail.com> wrote:

> I'm running Debian Buster. Inside a terminal window I can use Emacs and
> can see and enter Unicode chars.
>
...

Thanks all. I looked at my config files (which go back at least 15 years)
and found lots of explicitly setting both LC_ALL=C and LC_LANG=C.

Should I remove all, or just remove the LC_ALL?

-Tom

[toc] | [next] | [standalone]


#235303

FromIL Ka <kazakevichilya@gmail.com>
Date2021-05-18 18:40 +0200
Message-ID<CgaVb-5Gg-1@gated-at.bofh.it>
In reply to#235302

[Multipart message — attachments visible in raw view] — view raw

>
>
> Thanks all. I looked at my config files (which go back at least 15 years)
> and found lots of explicitly setting both LC_ALL=C and LC_LANG=C.
>
> Should I remove all, or just remove the LC_ALL?
>

> Using LC_ALL is strongly discouraged as it overrides everything. Please
use it only when testing and never set it in a startup file.
https://wiki.debian.org/Locale

It is better to set everything explicitly in "/etc/default/locale"

Even better: use
$ sudo dpkg-reconfigure locales
it will generate all locales you need AND set the default one in this file.

There is NO reason to use anything except UTF-8 in 2021




>

[toc] | [prev] | [next] | [standalone]


#235306

From"hdv@gmail" <hdv.jadev@gmail.com>
Date2021-05-18 19:10 +0200
Message-ID<Cgboe-65o-3@gated-at.bofh.it>
In reply to#235303
On 2021-05-18 18:37, IL Ka wrote:
> 
>     Thanks all. I looked at my config files (which go back at least 15
>     years) and found lots of explicitly setting both LC_ALL=C and LC_LANG=C.
> 
>     Should I remove all, or just remove the LC_ALL?
> 
> 
>  > Using LC_ALL is strongly discouraged as it overrides everything. 
> Please use it only when testing and never set it in a startup file.
> https://wiki.debian.org/Locale <https://wiki.debian.org/Locale>
> 
> It is better to set everything explicitly in "/etc/default/locale"
> 
> Even better: use
> $ sudo dpkg-reconfigure locales
> it will generate all locales you need AND set the default one in this file.
> 
> There is NO reason to use anything except UTF-8 in 2021

Please, be aware that not all Desktop Environments (like KDE's Plasma) 
honour this setting. Often, they have their own mechanisms for setting 
the locale within the DE itself.

Grx HdV

[toc] | [prev] | [next] | [standalone]


#235309

FromEike Lantzsch ZP6CGE <zp6cge@gmx.net>
Date2021-05-18 20:40 +0200
Message-ID<CgcNl-6Mg-7@gated-at.bofh.it>
In reply to#235306
On Dienstag, 18. Mai 2021 13:04:00 -04 hdv@gmail wrote:
> On 2021-05-18 18:37, IL Ka wrote:
> >     Thanks all. I looked at my config files (which go back at least
> >     15
> >     years) and found lots of explicitly setting both LC_ALL=C and
> >     LC_LANG=C.
> >
> >     Should I remove all, or just remove the LC_ALL?
> >  >
> >  > Using LC_ALL is strongly discouraged as it overrides everything.
> >
> > Please use it only when testing and never set it in a startup file.
> > https://wiki.debian.org/Locale <https://wiki.debian.org/Locale>
> >
> > It is better to set everything explicitly in "/etc/default/locale"
> >
> > Even better: use
> > $ sudo dpkg-reconfigure locales
> > it will generate all locales you need AND set the default one in
> > this file.
> >
> > There is NO reason to use anything except UTF-8 in 2021
>
> Please, be aware that not all Desktop Environments (like KDE's Plasma)
> honour this setting. Often, they have their own mechanisms for
> setting the locale within the DE itself.
>
> Grx HdV

To noboy in particular:
Yes, that is so and for whatever reasons there might be, it is extremely
confusing causing frustration, despair and eventually anger.
It is especially exasperating if one works with several DE which,
contrary to the underlying distribution, also change their behaviour
once in awhile.
I used to have en_US language with German keyboard and SA-paraguaian
monetary symbols. That is an edge-case which worked fine for many years
but recently gives me trouble with KDE and also Perl.
 Cheers to everybody on the list

--
Eike Lantzsch ZP6CGE

[toc] | [prev] | [next] | [standalone]


#235316

Fromdeloptes <deloptes@gmail.com>
Date2021-05-18 21:20 +0200
Message-ID<Cgdq2-7f9-17@gated-at.bofh.it>
In reply to#235309
Eike Lantzsch ZP6CGE wrote:

> To noboy in particular:
> Yes, that is so and for whatever reasons there might be, it is extremely
> confusing causing frustration, despair and eventually anger.
> It is especially exasperating if one works with several DE which,
> contrary to the underlying distribution, also change their behaviour
> once in awhile.
> I used to have en_US language with German keyboard and SA-paraguaian
> monetary symbols. That is an edge-case which worked fine for many years
> but recently gives me trouble with KDE and also Perl.
> Cheers to everybody on the list

This is why I decided to stick to the continuation of KDE3 now called TDE -
using Cyrillic, German and English - no issues.
I refused to be victim of developers/designers dictatorship.
TDE might not be perfect, but the community wants to have stable desktop.

It could also work with newer KDE if it were possible to find one stable
version and stick to it. However your post and similar are not very
motivational to try newer KDE again soon.

[toc] | [prev] | [next] | [standalone]


#235428

FromTom Browder <tom.browder@gmail.com>
Date2021-05-20 14:20 +0200
Message-ID<CgPOF-5lW-1@gated-at.bofh.it>
In reply to#235303

[Multipart message — attachments visible in raw view] — view raw

On Tue, May 18, 2021 at 11:37 IL Ka <kazakevichilya@gmail.com> wrote
…

Thanks!

-Tom

[toc] | [prev] | [next] | [standalone]


#235328

FromGreg Wooledge <greg@wooledge.org>
Date2021-05-18 19:40 +0200
Message-ID<CgbRg-6eg-7@gated-at.bofh.it>
In reply to#235302
On Tue, May 18, 2021 at 11:24:39AM -0500, Tom Browder wrote:
> Thanks all. I looked at my config files (which go back at least 15 years)
> and found lots of explicitly setting both LC_ALL=C and LC_LANG=C.
> 
> Should I remove all, or just remove the LC_ALL?

LC_LANG isn't even a variable that actually gets used.  Maybe it's a typo
that you made which had no observable negative effects, so it just hung
around.

I would remove both, for sure.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web