unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21472@debbugs.gnu.org
Subject: bug#21472: 25.0.50; REGRESSION: (emacs) `Coding Systems' uses curly quotes for Lisp strings
Date: Wed, 16 Sep 2015 13:31:28 -0700	[thread overview]
Message-ID: <55F9D1A0.5060804@cs.ucla.edu> (raw)
In-Reply-To: <83bnd26wns.fsf@gnu.org>

On 09/16/2015 11:34 AM, Eli Zaretskii wrote:
> "push", "wheel", etc. aren't technical terms,

Sure they are.  And they're commonly used that way nowadays, e.g.:

https://github.com/jquery/jquery-mousewheel
https://lists.gnu.org/archive/html/emacs-diffs/2013-10/msg00185.html
http://git-scm.com/docs/git-push
https://lists.gnu.org/archive/html/emacs-devel/2014-11/msg01746.html

Omitting unnecessary quotes would help improve on the stuffy and dated 
feel that the Emacs manuals too often have.  A part of this stuffiness 
comes from quoting terms that may have been newfangled decades ago but 
are in common use now.  Repeatedly quoting now-common terms like "push", 
"mouse wheel", "cut", "copy", and "minimize" makes the manuals look like 
they were written decades ago and haven't been properly updated since.  
(Look, Ma!  I can "cut" from this window and "paste" into this other one 
with my "mouse wheel"! :-)





  reply	other threads:[~2015-09-16 20:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13 15:45 bug#21472: 25.0.50; REGRESSION: (emacs) `Coding Systems' uses curly quotes for Lisp strings Drew Adams
2015-09-13 20:07 ` Eli Zaretskii
2015-09-13 21:11   ` Drew Adams
2015-09-14  6:24     ` Eli Zaretskii
2015-09-14 14:08 ` Richard Stallman
2015-09-15 15:57 ` Paul Eggert
2015-09-15 16:00   ` Eli Zaretskii
2015-09-15 16:22     ` Paul Eggert
2015-09-15 23:48       ` Drew Adams
2015-09-15 16:26   ` Eli Zaretskii
2015-09-15 19:15     ` Paul Eggert
2015-09-15 23:48       ` Drew Adams
2015-09-16  6:56       ` Eli Zaretskii
2015-09-16  7:32         ` Eli Zaretskii
2015-09-16  7:48         ` Paul Eggert
2015-09-16 10:02           ` Eli Zaretskii
2015-09-15 23:48     ` Drew Adams
2015-09-15 23:48   ` Drew Adams
2015-09-16  7:23     ` Eli Zaretskii
2015-09-16  7:49       ` Paul Eggert
2015-09-16 10:07         ` Eli Zaretskii
2015-09-16 15:31           ` Paul Eggert
2015-09-16 17:18             ` Eli Zaretskii
2015-09-16 18:27               ` Paul Eggert
2015-09-16 18:34                 ` Eli Zaretskii
2015-09-16 20:31                   ` Paul Eggert [this message]
2015-09-17  4:46                     ` Eli Zaretskii
2015-09-17  5:21                       ` Paul Eggert
2015-09-17  6:03                         ` Eli Zaretskii
2015-09-17  7:21                           ` Paul Eggert
2015-09-17  7:35                             ` Eli Zaretskii
     [not found]   ` <<831tdz8yf8.fsf@gnu.org>
2015-09-15 23:48     ` Drew Adams
     [not found] <<c7ebc07d-51c9-4d10-9238-d42b0b3845b7@default>
     [not found] ` <<83vbbe9j7k.fsf@gnu.org>
     [not found]   ` <<661f3a80-cdaf-47f0-a096-4be744409150@default>
     [not found]     ` <<83pp1la58d.fsf@gnu.org>
2015-09-14 13:51       ` Drew Adams
2015-09-15  0:21         ` Richard Stallman
     [not found] ` <<55F83FDF.2070202@cs.ucla.edu>
     [not found]   ` <<3aa1fafa-ed4d-4935-8a3e-cae7d0842c5f@default>
     [not found]     ` <<83r3ly7rpd.fsf@gnu.org>
2015-09-16 15:16       ` Drew Adams

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=55F9D1A0.5060804@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=21472@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).