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] Doc string for org-clock-into-drawer truncated?
Date: Sun, 26 Jun 2011 17:27:19 +0200	[thread overview]
Message-ID: <87vcvswr3c.fsf@Rainer.invalid> (raw)
In-Reply-To: 4E0061E4.5070704@wilkesley.net

Ian Barton <lists@wilkesley.net> writes:
>>> The default for this variable is the value of `org-log-into-drawer',
>>> which see."
>>> …
>>> I can't make much sense of the last sentence which looks truncated.
>> It means, please look at the variable org-log-into-drawer for
>> more information.  I have seen this idiom in Emacs
>> in a number of places, so I assumed it is OK.
> I agree with Achim, that idiom makes no sense to a native English
> speaker. To make sense it should say something like ".... for which
> see the doc string for `org-log-into-drawer', or even better the way
> Achim's patch is worded.

I've looked through some Emacs documentation and it is indeed the case
that ", which see." or "(which see)" is used in many places to make
reference to the documentation of a variable or function that has been
mentioned by name.  I'll just leave it at that and suggest it might be
discussed on an appropriate Emacs list if necessary.

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

SD adaptation for Waldorf microQ V2.22R2:

  reply	other threads:[~2011-06-26 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 19:32 [Bug] Doc string for org-clock-into-drawer truncated? Achim Gratz
2011-06-21  7:49 ` Carsten Dominik
2011-06-21  9:18   ` Ian Barton
2011-06-26 15:27     ` Achim Gratz [this message]
2011-06-22 21:11   ` Achim Gratz
2011-06-26 16:10   ` [PATCH] Introduce CLOCK_INTO_DRAWER property like the existing LOG_INTO_DRAWER (was: [Bug] Doc string for org-clock-into-drawer truncated?) Achim Gratz
2011-06-27 10:14     ` [PATCH] Introduce CLOCK_INTO_DRAWER property like the existing LOG_INTO_DRAWER Bastien
2011-06-27 19:52       ` Achim Gratz
2011-06-28 16:38         ` 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:

  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=87vcvswr3c.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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