From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Trouble with autofill mode
Date: Mon, 03 Aug 2015 21:12:02 -0400 [thread overview]
Message-ID: <871tfjvov1.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: 5AF0D5A1-1F17-44EF-900F-A165757DC745@agrarianresearch.org
Vikas Rawal <vikaslists@agrarianresearch.org> writes:
>>
>>> I am inserting LaTeX \index{} commands in an org document to create an
>>> index. Almost everything works fine. But I am having trouble with
>>> auto-fill-mode. It often puts a line break in the middle of an index
>>> entry, and then it does not work.
>>>
>>> That is, \index{my name} is sometimes broken into \index{my
>>> name}. This creates a problem for LaTeX.
>>>
>>> I have disabled auto-fill-mode for now, but that is clearly
>>> a sub-optimal thing to do. Is there a way to tell it not to put line
>>> breaks in the middle of \index{} entries?
>>
>> Have you tried
>>
>> #+INDEX: my name
>>
>> Regards,
>>
>
>
> I am sorry for not being clear. \index{} may have to be used inline in
> a para since the index has to pick up the right page where a term
> appears. So you want to put it as close as possible to the keywords.
>
So put it as close as possible to the keywords:
--8<---------------cut here---------------start------------->8---
This section needs to index some
#+INDEX: multi word term
multi word terms.
--8<---------------cut here---------------end--------------->8---
--
Nick
next prev parent reply other threads:[~2015-08-04 1:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 18:54 Trouble with autofill mode Vikas Rawal
2015-08-02 20:18 ` Nicolas Goaziou
2015-08-03 0:05 ` Vikas Rawal
2015-08-04 1:12 ` Nick Dokos [this message]
2015-08-04 3:11 ` Vikas Rawal
2015-08-04 3:39 ` Ken Mankoff
2015-08-04 4:22 ` Vikas Rawal
2015-08-04 12:47 ` John Kitchin
2015-08-04 14:08 ` Eric S Fraga
2015-08-05 8:17 ` Sebastien Vauban
2015-08-05 9:31 ` Eric S Fraga
-- strict thread matches above, loose matches on Subject: below --
2015-08-03 3:07 Vicente Vera
2015-08-03 3:12 ` Vikas Rawal
2015-08-04 1:04 ` Vikas Rawal
2015-08-04 14:10 ` John Kitchin
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=871tfjvov1.fsf@pierrot.dokosmarshall.org \
--to=ndokos@gmail.com \
--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).