unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 20707@debbugs.gnu.org
Subject: bug#20707: [PROPOSED PATCH] Use curved quoting in C-generated errors
Date: Tue, 2 Jun 2015 17:07:24 +0000	[thread overview]
Message-ID: <20150602170724.GA2567@acm.fritz.box> (raw)
In-Reply-To: <556DCE36.9070505@cs.ucla.edu>

Hello, Paul.

On Tue, Jun 02, 2015 at 08:39:34AM -0700, Paul Eggert wrote:
> Alan Mackenzie wrote:

> > What I really meant with my question is how do you type curly characters
> > when outwith Emacs?  Say, inside of less, or at a bash shell prompt, or
> > in any of numerous other tools one might wish to use?

> It doesn't come up that often, but for 'less' I am typically searching and 
> searching for '.' will do -- I sometimes do that even for ASCII-only searches, 
> as '.' is easier to type than, say, '\'.  I typically run Bash under Emacs where 
> it's not a problem there either.

> In the rarer cases where I'm outside Emacs or want to search just for curved 
> quotes and nothing else, I can type Compose < ' and Compose > ' to get curved 
> single quotes.  On my current keyboard, the Compose key looks like a menu and is 
> just to the right of the right Alt key; this is the default setup that came with 
> Ubuntu 15.04.  I'm sure one can get the Compose key to work on the Linux console 
> too, as plenty of people need to type accented letters on the Linux console.

There appears to be provision for a compose key in the Linux terminal,
yes; it's partially documented in man loadkeys.

> > it's yet another trivial annoyance that one has to heep onto all

> Heh.  Trivial annoyances are what motivated this change.  I've been trivially 
> annoyed at Emacs quoting `like this' for at least a decade.  Nearly every other 
> GNU package has fixed it.  I was hoping Somebody Else would fix it for Emacs, 
> but nobody ever stepped up so here we are.

You're breaking things.  Right now, Emacs works in "any" environment, and
I think this was a positive design decision way back when.  You're now
changing Emacs so that its proper working is restricted to UTF-8
environemnts, which is fine for you because you run under such.

As I've suggested before, why don't you make --with-curly-quotes a
configuration option?

-- 
Alan Mackenzie (Nuremberg, Germany).





  parent reply	other threads:[~2015-06-02 17:07 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 [this message]
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
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=20150602170724.GA2567@acm.fritz.box \
    --to=acm@muc.de \
    --cc=20707@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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).