unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Alan Mackenzie <acm@muc.de>
Cc: 20707@debbugs.gnu.org
Subject: bug#20707: [PROPOSED PATCH] Use curved quoting in C-generated errors
Date: Thu, 11 Jun 2015 19:41:54 -0700	[thread overview]
Message-ID: <557A46F2.50201@cs.ucla.edu> (raw)
In-Reply-To: <20150611190640.GA2752@acm.fritz.box>

Alan Mackenzie wrote:

> My setup couldn't display curly single quotes

Sure it could.  It displayed curved single quotes as curved single quotes.  Your 
objection was that your setup also displayed grave accent and apostrophe as 
curved single quotes (a style you happen to prefer), and you wanted your setup 
to display *different-shaped curves* for curved single quotes.  This will not be 
not a problem to the few ordinary Emacs users who happen to use a similar 
obsolescent environment; they'll merely see nicely curved single quotes and move on.

> none of them that I've
> seen so far have distinct glyphs for the curly quotes.

Again, distinct glyphs are not a requirement for ordinary Emacs users.  That 
being said, for Emacs developers such as yourself, the Lat15-Terminus16 font I 
mentioned earlier has distinct glyphs for curved quotes, as does 
Lat15-TerminusBold16.  You can find them archived at 
<http://bugs.gnu.org/20707>.  There are many other choices in this area.

> That easiness remains controversial.

It's certainly easier to read text quoted ‘like this’ than to read text quoted 
\`like this\'.

> To be useful, it would have to become the standard way of quoting
> symbols.

I doubt whether it'll be the standard.  It's uglier and more complicated than 
the alternative.  Its main advantage is that it's easier to type for users who 
want to type only ASCII.

> Where do you see any portability hassles?

Code might work when running on a typical Emacs system, but might fail on an 
Emacs system configured --without-curved-quotes, because Emacs will generate 
different strings that will be treated differently.

> What exactly do you mean by "display problems fixed"?

On the rare systems that don't display curved quotes as quotes, Emacs should 
display straight quotes as substitutes.  That's good enough for these rare and 
obsolescent systems.

> I don't think it's TRT simply to curlify any quote typed within a string

Electric Quote mode doesn't do that.  If you type an apostrophe, it normally 
leaves the apostrophe alone.  And in the rare cases where one really wants a 
grave accent and not a left single quote, it's easy enough to type C-q `.

> How about only curlifying when
> there's a matched pair of quotes containing exactly a symbol, and
> uncurlifying when that ceases to be the case?

That wouldn't work well; for example, it'd mishandle the common case of "`%s'". 
  Worse, it'd mean that Emacs couldn't curve the open quote until the user types 
the corresponding closed quote.  I experimented with several approaches along 
the lines you're suggesting, and they all had action-at-a-distance problems that 
made for confusing UIs.  It's much better if quotes are curved only when near 
the cursor, so users see them being curved.





  reply	other threads:[~2015-06-12  2:41 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01  7:39 bug#20707: [PROPOSED PATCH] Use curved quoting in C-generated errors Paul Eggert
     [not found] ` <mailman.4052.1433144480.904.bug-gnu-emacs@gnu.org>
2015-06-01 10:49   ` Alan Mackenzie
2015-06-01 16:01     ` Paul Eggert
2015-06-01 17:17       ` Alan Mackenzie
2015-06-01 18:50         ` Paul Eggert
2015-06-02 11:56           ` Alan Mackenzie
2015-06-02 13:25             ` Drew Adams
2015-06-02 15:39             ` Paul Eggert
2015-06-02 15:51               ` Dmitry Gutov
2015-06-02 20:05                 ` Paul Eggert
2015-06-02 17:07               ` Alan Mackenzie
2015-06-02 20:44                 ` Alan Mackenzie
2015-06-04 15:43                   ` Paul Eggert
2015-06-06 15:54                     ` Alan Mackenzie
2015-06-06 18:11                       ` Paul Eggert
2015-06-06 20:50                         ` Alan Mackenzie
2015-06-07  0:09                           ` Paul Eggert
2015-06-08 17:18                             ` Alan Mackenzie
2015-06-09  6:53                               ` Paul Eggert
2015-06-09 13:34                                 ` Alan Mackenzie
2015-06-09 20:49                                   ` Paul Eggert
2015-06-09 22:46                                     ` Alan Mackenzie
2015-06-09 23:42                                       ` Paul Eggert
2015-06-10 13:39                                         ` Alan Mackenzie
2015-06-10 16:20                                           ` Paul Eggert
2015-06-10 17:39                                             ` Dmitry Gutov
2015-06-10 19:42                                               ` Paul Eggert
2015-06-10 19:17                                             ` Alan Mackenzie
2015-06-10 19:44                                               ` Paul Eggert
2015-06-11 19:06                                                 ` Alan Mackenzie
2015-06-12  2:41                                                   ` Paul Eggert [this message]
2015-06-12 11:25                                                     ` Alan Mackenzie
2015-06-12 23:46                                                       ` Paul Eggert
2015-06-13 11:54                                                         ` Alan Mackenzie
2015-06-13 17:54                                                           ` Paul Eggert
2015-06-07 13:17                       ` Wolfgang Jenkner
2015-06-09 16:58                         ` Alan Mackenzie
2015-06-02 23:26                 ` Paul Eggert
2015-06-01 14:34 ` Eli Zaretskii
2015-06-01 16:48   ` Glenn Morris
2015-06-01 17:55   ` Paul Eggert
2015-06-01 18:29     ` Eli Zaretskii
2015-06-01 21:13     ` Stefan Monnier
2015-06-09 19:44 ` Wolfgang Jenkner
2015-06-11 13:06 ` bug#20707: " Andy Moreton
2020-08-12 13:02 ` bug#20707: [PROPOSED PATCH] " Lars Ingebrigtsen

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=557A46F2.50201@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=20707@debbugs.gnu.org \
    --cc=acm@muc.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.
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).