emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [DEV] Text quoting backports
Date: Sun, 06 Sep 2015 10:43:31 -0400	[thread overview]
Message-ID: <87mvwzip64.fsf@kyleam.com> (raw)
In-Reply-To: <loom.20150906T151713-198@post.gmane.org> (rasmus@gmx.us's message of "Sun, 6 Sep 2015 13:24:11 +0000 (UTC)")

Rasmus <rasmus@gmx.us> writes:

> Isn't this dependent on Emacs 25? Currently maint target emacs 23 and master
> targets 24.3.

They will only affect Emacs 25 users, but IIUC none of these would break
the any supported Emacs versions.

If the Emacs version doesn't have functions that look at
text-quoting-style and change the output, quotes should appear how they
do in the source.  This is part of my motivation for wanting to revert
the s/'.*'/‘.*’/ and s/`.*'/‘.*’/ changes.  That way, if the installed
Emacs has a function that substitutes based on text-quoting-style, fine.
Otherwise, things look how they did.

The one new function is format-message, which is given a defalias to
format if it's not defined.  So again, things should continue as usual
when not running Emacs 25.

The changes that protect single quotes in docstrings will work in
earlier versions, but they are needed in Emacs 25 to avoid

 (setq org-agenda-custom-commands
   '((\"h\" . \"HOME + Name tag searches\") ; describe prefix \"h\"
 ...

being displayed in the help buffer as

   (setq org-agenda-custom-commands
   ’(("h" . "HOME + Name tag searches") ; describe prefix "h"
   ...

--
Kyle

  reply	other threads:[~2015-09-06 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06  6:12 [DEV] Text quoting backports Kyle Meyer
2015-09-06 13:24 ` Rasmus
2015-09-06 14:43   ` Kyle Meyer [this message]
2015-09-07 19:18 ` Nicolas Goaziou

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mvwzip64.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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/org-mode.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).