unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michal Nazarewicz <mina86@mina86.com>
To: rms@gnu.org
Cc: emacs-devel@gnu.org, yuri.v.khan@gmail.com
Subject: Re: Electric punctuation mode
Date: Thu, 04 Feb 2016 14:54:22 +0100	[thread overview]
Message-ID: <xa1tio24mvht.fsf@mina86.com> (raw)
In-Reply-To: <E1aR6J2-0002GI-9J@fencepost.gnu.org>

On Wed, Feb 03 2016, Richard Stallman wrote:
>   > Yes, I’ve been thinking about this overnight and stared wondering
>   > whether a better solution wouldn’t be a mode for HTML documents which
>   > would automatically convert between Unicode characters when editing and
>   > entities when stored on disk.
>
> That might work ok -- I'd have to try it before I could judge.

This all depends what the actual desired behaviour is.

1. If you care about having the file in US-ASCII, having entities be
   translated when reading and saving the file would work.  Of course
   a good question is why one would limit their HTML files to ASCII.

2. If you care about having entities when editing, than the
   aforementioned schema would not work.  Honestly though, I’m somehow
   surprised that you’d prefer HTML entities to proper Unicode
   characters.

The first would be outside of the scope of electrict-punc-mode, the
second would require a custom rule set which, as I described, is doable.

-- 
Best regards
Liege of Serenely Enlightened Majesty of Computer Science,
ミハウ “mina86” ナザレヴイツ  <mpn@google.com> <xmpp:mina86@jabber.org>



  reply	other threads:[~2016-02-04 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 16:37 Electric punctuation mode Michal Nazarewicz
2016-02-02 23:11 ` Richard Stallman
2016-02-03  1:22   ` Michal Nazarewicz
2016-02-03 10:20     ` Yuri Khan
2016-02-03 12:17       ` Michal Nazarewicz
2016-02-03 13:20         ` Stefan Monnier
2016-02-03 22:53         ` Richard Stallman
2016-02-04 13:54           ` Michal Nazarewicz [this message]
2016-02-03 22:53       ` Richard Stallman
2016-02-03 15:39     ` Richard Stallman
2016-02-04 13:50       ` Michal Nazarewicz
2016-02-03  2:39 ` Paul Eggert

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=xa1tio24mvht.fsf@mina86.com \
    --to=mina86@mina86.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=yuri.v.khan@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).