emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] aorg-agenda effort filter
Date: Thu, 29 May 2014 11:03:49 +0200	[thread overview]
Message-ID: <878uplx8ga.fsf@Rainer.invalid> (raw)
In-Reply-To: 87ha4939zu.fsf@bzg.ath.cx

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

I can't find this stipulation anywhere in the official docs.

https://www.gnu.org/software/emacs/manual/html_node/emacs/Format-of-ChangeLog.html
https://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html

Clearly the quoting style used in the changelog entries follows the GNU
coding style, which has now changed from the former preference of using
backticks as the left quote character to single quotes (the second
document already uses the new style in the example).  In fact it isn't
even talking about needing to always use quotes (it is more consistent
to always use them, but at least for prefixed names there is no
ambiguity of what was meant to begin with).

> No, the convention is still to use ` for variables in change logs.

You might ask Stefan for a policy decision, although I can't see why the
Emacs project would deviate from the GNU coding standard in this regard.

> 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.)

Now you're talking about docstrings and I'll expect that this will also
change, albeit much more slowly.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

next prev parent reply	other threads:[~2014-05-29  9:04 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
2014-05-29  9:03           ` Achim Gratz [this message]
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=878uplx8ga.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

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).