unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Unicode and text editors
Date: Sun, 08 Dec 2024 19:39:55 +0000	[thread overview]
Message-ID: <Be0XIegjOn-QFIHzjODCIV_jnl-68E45AFCdDLeqeQ6cYw8sH6hMgQudQVXE_Jx4REYEV96IgFMaEtOaIlDTWDY7QbsIDrY61z-feuEjIpM=@protonmail.com> (raw)
In-Reply-To: <86wmgadmd8.fsf@gnu.org>


On Monday, December 9th, 2024 at 7:07 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> > Date: Sun, 08 Dec 2024 18:55:52 +0000
> > From: Heime heimeborgia@protonmail.com
> > Cc: help-gnu-emacs@gnu.org
> > 
> > > I was talking about Emacs. Your original question was about other
> > > editors. I'm not familiar with other modern editors enough to tell
> > > whether you should or should not worry. In particular, I don't know
> > > how they recognize UTF-8, and am not sure that Emacs coding cookies
> > > are supported by them.
> > 
> > Is it reasonable to expect that UTF-* characters are recognised and supported?
> 
> 
> Reasonable? yes. But the problem is not trivial: Emacs itself not
> always recognizes UTF-8 reliably. So there could be problems.
> 
> > What is your school of thought regarding emacs?
> 
> 
> I don't understand the question, sorry.

Should we comfortable use UTF Characters in source code when using Emacs?
When there are problems, do they usually get looked into and fixed if possible? 




  reply	other threads:[~2024-12-08 19:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-08 13:16 Unicode and text editors Heime via Users list for the GNU Emacs text editor
2024-12-08 13:29 ` Jean Louis
2024-12-08 13:31 ` Basile Starynkevitch
2024-12-08 14:02   ` Heime via Users list for the GNU Emacs text editor
2024-12-08 15:15     ` W. Greenhouse via Users list for the GNU Emacs text editor
2024-12-08 16:32       ` Eli Zaretskii
2024-12-08 17:54         ` Heime via Users list for the GNU Emacs text editor
2024-12-08 18:44           ` Eli Zaretskii
2024-12-08 18:55             ` Heime via Users list for the GNU Emacs text editor
2024-12-08 19:07               ` Eli Zaretskii
2024-12-08 19:39                 ` Heime via Users list for the GNU Emacs text editor [this message]
2024-12-08 20:43                   ` Eli Zaretskii
2024-12-08 20:48                     ` Heime via Users list for the GNU Emacs text editor
2024-12-09  3:24                       ` Eli Zaretskii
2024-12-09  3:35                   ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-08 16:06 ` Stefan Monnier via Users list for the GNU Emacs text editor

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='Be0XIegjOn-QFIHzjODCIV_jnl-68E45AFCdDLeqeQ6cYw8sH6hMgQudQVXE_Jx4REYEV96IgFMaEtOaIlDTWDY7QbsIDrY61z-feuEjIpM=@protonmail.com' \
    --to=help-gnu-emacs@gnu.org \
    --cc=eliz@gnu.org \
    --cc=heimeborgia@protonmail.com \
    /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).