From: Carsten Dominik <carsten.dominik@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: variable names in manual
Date: Fri, 26 Apr 2013 12:11:46 +0200 [thread overview]
Message-ID: <5B2184C7-1E7F-439E-96CD-275409C85EA5@gmail.com> (raw)
In-Reply-To: <20130426095924.GA23639@kuru.dyndns-at-home.com>
On 26 apr. 2013, at 11:59, Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> Hi Bastien and Carsten,
>
> On Fri, Apr 26, 2013 at 11:27:04AM +0200, Bastien wrote:
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> Yes, I agree. Let's wait for Bastien to take a last look at this,
>>> but it should indeed be reverted.
>>
>> Oh, I wasn't aware of this "metasyntactical" notion.
>> No problem for reverting this change -- please make this
>> in the maint branch so that users of 8.0.2 enjoy this.
>> Also, maybe the revert of this commit is not enough,
>> and we should check against remaining @var{...} to see
>> if they are okay.
>
> I did a query-replace-regexp: @var{\([^}]+\)} -> @code{\1}. Hopefully I
> skipped the right ones; patch is attached.
Do you have write access? If so, please install you patch.
- Carsten
>
> Cheers,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
> <0001-Switch-var-macros-to-code-for-lisp-variables.patch>
next prev parent reply other threads:[~2013-04-26 10:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 23:37 variable names in manual Greg Minshall
2013-04-25 23:48 ` Suvayu Ali
2013-04-26 7:45 ` Carsten Dominik
2013-04-26 8:10 ` Carsten Dominik
2013-04-26 8:41 ` Suvayu Ali
2013-04-26 8:46 ` Carsten Dominik
2013-04-26 9:27 ` Bastien
2013-04-26 9:59 ` Suvayu Ali
2013-04-26 10:11 ` Carsten Dominik [this message]
2013-04-26 10:27 ` Suvayu Ali
2013-04-26 10:31 ` Carsten Dominik
2013-04-26 6:56 ` Bastien
2013-04-26 7:21 ` Suvayu Ali
2013-04-26 7:50 ` Bastien
2013-04-26 11:03 ` Greg Minshall
2013-04-26 12:29 ` Bastien
2013-04-26 13:40 ` Greg Minshall
-- strict thread matches above, loose matches on Subject: below --
2013-04-25 23:33 Greg Minshall
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=5B2184C7-1E7F-439E-96CD-275409C85EA5@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.com \
/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).