emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Tassilo Horn <tassilo@member.fsf.org>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: keys and command name info
Date: Sun, 08 Aug 2010 15:57:00 +0200	[thread overview]
Message-ID: <4C5EB7AC.1060209@easy-emacs.de> (raw)
In-Reply-To: <352C0CDC-18DB-4CC0-B1CD-7F6E3CB106F6@gmail.com>

Am 07.08.2010 21:39, schrieb Carsten Dominik:
>
> On Jul 30, 2010, at 11:40 AM, Andreas Röhler wrote:
>
>> Am 29.07.2010 20:08, schrieb Tassilo Horn:
>>> Andreas Röhler<andreas.roehler@easy-emacs.de> writes:
>>>
>>>> attached another patch replacing the former, due to a bug at texi
>>>
>>> Please also add @findex{} entries.
>>>
>>> Bye,
>>> Tassilo
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Please use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>
>>
>> Done. Patch attached.
>>
>> Seems the functions index node remains to write.
>>
>> Looking into, I see a strange thing at line 14746:
>>
>> @node Variable Index, , Key Index, Top
>
> What is wrong with this line?
> I remember having some problems with the document structure
> around the index - but somehow I am blind to see what is wrong.
> Apparently you see something - what is it?
>
> - Carsten
>

Hi Carsten,

empty space with colon followed by empty space looks strange for me.
Didn't mean wrong, just strange.

Just a question.

BTW, what's with the patch?
Do you want it?

If yes, I'll insert the index entry near this place still.

Andreas

  reply	other threads:[~2010-08-08 16:43 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 19:36 keys and command name info Andreas Röhler
2010-07-29  6:45 ` Tassilo Horn
2010-07-29 13:47   ` Andreas Röhler
2010-07-29 15:19     ` Andreas Röhler
2010-07-29 18:08       ` Tassilo Horn
2010-07-30  9:40         ` Andreas Röhler
2010-08-07 19:39           ` Carsten Dominik
2010-08-08 13:57             ` Andreas Röhler [this message]
2010-07-31  8:53     ` Bastien
2010-07-31 17:53       ` Andreas Röhler
2010-07-31 19:02         ` Thomas S. Dye
2010-08-01  9:42         ` Bastien
2010-08-01 16:40           ` Andreas Röhler
2010-08-02  6:32 ` Carsten Dominik
2010-08-08 22:26   ` Gregor Zattler
2010-08-09  6:43     ` Carsten Dominik
2010-08-09  9:37       ` Andreas Burtzlaff
2010-08-09 10:19         ` Gregor Zattler
2010-08-09 10:31           ` Carsten Dominik
2010-08-09 18:32           ` Dan Davison
2010-08-09 19:28             ` Dan Davison
2010-08-11 10:05               ` Carsten Dominik
2010-08-11 10:23                 ` Andreas Röhler
2010-08-11 10:27                   ` Carsten Dominik
2010-08-13 13:45                 ` Andreas Röhler
2010-08-13 14:20                   ` Dan Davison
2010-08-13 19:30                 ` Andreas Röhler
2010-08-15  7:37                   ` Carsten Dominik
2010-08-15  7:39                     ` Carsten Dominik
2010-08-15 19:07                       ` Andreas Röhler
2010-08-16  8:57                         ` Carsten Dominik
2010-08-17 12:43                           ` Andreas Röhler
2010-08-18  8:38                             ` Carsten Dominik
2010-08-20  6:27                               ` Andreas Röhler
2010-08-20  7:31                                 ` Carsten Dominik
2010-08-20  8:13                                   ` Andreas Röhler
2010-08-20  7:44                                 ` Carsten Dominik
2010-08-17 15:44                           ` Andreas Röhler
2010-08-10  1:28             ` Memnon Anon
2010-08-09 14:23       ` Nick Dokos
2010-08-10  7:48       ` OT: smex.el (was Re: keys and command name info) Austin Frank
2010-08-20 11:20 ` keys and command name info Carsten Dominik
2010-08-20 11:32   ` Stefan Vollmar
2010-08-20 13:23   ` Bernt Hansen

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=4C5EB7AC.1060209@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tassilo@member.fsf.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).