emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Reuben Thomas <rrt@sc3d.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: It's not obvious how to keep LocalWords (spelling exceptions) conveniently [8.2.10 (release_8.2.10 @ /usr/share/emacs/24.4/lisp/org/)]
Date: Tue, 30 Jun 2015 15:35:08 +0200	[thread overview]
Message-ID: <87si99iak3.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87y4j1346c.fsf@sc3d.org> (Reuben Thomas's message of "Tue, 30 Jun 2015 11:02:03 +0100")

Hello,

Reuben Thomas <rrt@sc3d.org> writes:

Disclaimer: I don't know what are "LocalWords" and I could find
a reference either in the Emacs or Elisp manual.

> I use flyspell/ispell, and add words to my org files’ LocalWords
> stanzas. I keep these at the bottom of my document (as is typical for
> other file types), but I don’t insist on that if there’s a better way.

Put them at the beginning of the file, i.e., before the first headline,
and comment them.

> The problem is that when I press Ctrl+Return near the bottom of the
> buffer, just above the LocalWords stanza, point skips past the commented
> LocalWords and makes a new entry underneath.

See above.

> However, it would be good if this worked out of the box, i.e. if if
> org-mode instrumented ispell suitably so that when LocalWords entries
> are added, they are a) by default not included in the export,

It will not happen if you comment them.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2015-06-30 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 10:02 Bug: It's not obvious how to keep LocalWords (spelling exceptions) conveniently [8.2.10 (release_8.2.10 @ /usr/share/emacs/24.4/lisp/org/)] Reuben Thomas
2015-06-30 13:35 ` Nicolas Goaziou [this message]
2015-06-30 14:08   ` Daniele Pizzolli
2015-06-30 16:57   ` Reuben Thomas

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=87si99iak3.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rrt@sc3d.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).