From: Filipe Silva <filipe.silva@gmail.com>
To: tomas@tuxteam.de
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: how to teach emacs that ' + c = ç
Date: Wed, 5 Jul 2017 18:26:40 -0300 [thread overview]
Message-ID: <CAEwkUWNPA4DUA8bwDQmM8o-RJaOMh5gdyx+f3a6qm=hPUudkDw@mail.gmail.com> (raw)
In-Reply-To: <20170705203810.GB2442@tuxteam.de>
Ok but there's No `C` Language environment on that list.
What exactly does LANG=C do to emacs?
On Wed, Jul 5, 2017 at 5:38 PM, <tomas@tuxteam.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, Jul 05, 2017 at 12:55:08PM -0300, Filipe Silva wrote:
> > very interesting. LANC=C emacs really fix the problem. What is happening
> > here?
> >
> > maybe this is a bug.
>
> There's mention on that in the doc (22.2 Language Environments):
>
> #+BEGIN_QUOTE
> To display information about the effects of a certain language
> environment LANG-ENV, use the command `C-h L LANG-ENV <RET>'
> (`describe-language-environment'). This tells you which languages this
> language environment is useful for, and lists the character sets,
> coding systems, and input methods that go with it. It also shows some
> sample text to illustrate scripts used in this language environment.
> If you give an empty input for LANG-ENV, this command describes the
> chosen language environment.
> #+END_QUOTE
>
> So it's probably intentional
>
> Cheers
> - -- tomás
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iEYEARECAAYFAlldTjIACgkQBcgs9XrR2kZtVgCfb/nfP+0tadgvJq/7oYJD1wOc
> 1AUAnjYlvXWPxwcbmq4pM9qrOvRqcmDR
> =zadJ
> -----END PGP SIGNATURE-----
>
>
next prev parent reply other threads:[~2017-07-05 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 1:25 how to teach emacs that ' + c = ç Filipe Silva
2017-07-05 1:57 ` Óscar Fuentes
2017-07-05 15:55 ` Filipe Silva
2017-07-05 16:11 ` Filipe Silva
2017-07-05 20:38 ` tomas
2017-07-05 21:26 ` Filipe Silva [this message]
2017-07-05 23:28 ` Filipe Silva
2017-07-05 6:14 ` Héctor Lahoz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEwkUWNPA4DUA8bwDQmM8o-RJaOMh5gdyx+f3a6qm=hPUudkDw@mail.gmail.com' \
--to=filipe.silva@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).