emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] aorg-agenda effort filter
Date: Wed, 28 May 2014 22:48:37 +0200	[thread overview]
Message-ID: <87ha4939zu.fsf@bzg.ath.cx> (raw)
In-Reply-To: <8761kpbraf.fsf@Rainer.invalid> (Achim Gratz's message of "Wed, 28 May 2014 22:07:52 +0200")

Achim Gratz <Stromeko@nexgo.de> writes:

> http://www.gnu.org/prep/standards/standards.html#index-left-quote
>
> The actual change to the document was made even earlier than I
> remembered:
>
> 2011-12-31  Paul Eggert  <eggert@cs.ucla.edu>
>
> 	* standards.texi (Quote Characters): change to recommending
> 	undirected quotes, '...' or "...".

This is about the quote character as an output, not as used in Emacs
change logs. 

>>> and EMACS is slowly following suit.
>>
>> Where do you see that Emacs is slowly following suit?
>
> There was a lengthy discussion around the latest version of makeinfo
> producing the new quoting style by default just recently and it has
> flared up before.  My takeaway from that was that EMACS would go with
> that change in coding style over time.

No, the convention is still to use ` for variables in change logs.
This is the same as using `variable' in Emacs lisp buffers (see line
343 of current trunk in lisp-mode.el, where `font-lock-constant-face'
is used for highlighting variables.)

-- 
 Bastien

  reply	other threads:[~2014-05-28 20:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 14:45 [bug] aorg-agenda effort filter Achim Gratz
2014-05-28 19:32 ` Bastien
2014-05-28 19:38   ` Achim Gratz
2014-05-28 19:46     ` Bastien
2014-05-28 20:07       ` Achim Gratz
2014-05-28 20:48         ` Bastien [this message]
2014-05-29  9:03           ` Achim Gratz
2014-05-29 17:12             ` Bastien

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=87ha4939zu.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@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/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).