From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] aorg-agenda effort filter
Date: Wed, 28 May 2014 22:07:52 +0200 [thread overview]
Message-ID: <8761kpbraf.fsf@Rainer.invalid> (raw)
In-Reply-To: 871tvd4rg1.fsf@bzg.ath.cx
Bastien writes:
> Achim Gratz <Stromeko@nexgo.de> writes:
>
>> Bastien writes:
>>> Also, the commit messages contain references like 'variable' instead
>>> of `variable'. A tiny difference, sure, but one that I will have to
>>> fix manually when merging the Changelogs into Emacs.
>>
>> The corresponding GNU coding standard has been changed about a year
>> ago
>
> Do you have a pointer?
http://www.gnu.org/prep/standards/standards.html#index-left-quote
The actual change to the document was made even earlier than I
remembered:
--8<---------------cut here---------------start------------->8---
2011-12-31 Paul Eggert <eggert@cs.ucla.edu>
* standards.texi (Quote Characters): change to recommending
undirected quotes, '...' or "...".
--8<---------------cut here---------------end--------------->8---
>> 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.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2014-05-28 20:08 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 [this message]
2014-05-28 20:48 ` Bastien
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=8761kpbraf.fsf@Rainer.invalid \
--to=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).