emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeffrey Spencer <jeffspencerd@gmail.com>
To: Bjarte Johansen <bjo013@student.uib.no>
Cc: emacs-orgmode@gnu.org
Subject: Re: More flyspell-overlays removed
Date: Sun, 29 Jul 2012 18:35:28 +1000	[thread overview]
Message-ID: <CALmFPZ2hw4jE81C0bvX-xaumYQOxa-SKOjZsuXMNKeSxTXwtdA@mail.gmail.com> (raw)
In-Reply-To: <0348D525-F0A3-4B85-9593-9704917CD9D9@student.uib.no>

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

I was also thinking about this recently but hadn't gotten as far as writing
a patch.

I was thinking some tags you know you want to remove the fly-spell overlays
but for example caption you might or might not want the flyspell overlays
removed. If there was a variable that could be set to choose some that
might or might not want the overlays to remove. Not sure if this is
possible but what I was originally looking at doing but hadn't gotten time.

Cheers,
Jeff

On Sun, Jul 29, 2012 at 8:38 AM, Bjarte Johansen <bjo013@student.uib.no>wrote:

> On 28 Jul, 2012, at 11:27 , Bastien <bzg@gnu.org> wrote:
>
> I cannot apply it because it adds keywords at the wrong place.
> For example you cannot add "startup:" in the first (cond ((...)))
> because "startup:" is not a "backend specific content."  And some
> other discrepencies.
>
>
> OK, I understand. I should have spent some more time trying to
> understand the code.
>
>
> I'd welcome a patch for removing more flyspell overlays, but it
> has to be rewritten.  I'm not using flyspell so someone else will
> have to do roll his sleeves.
>
>
> I'd be willing to put in the effort to make a proper patch, but I need
> some
> help to understand what is going on in this function. It is not obvious to
> me.
>
> The places flyspell-overlays needs to be removed are in the startup,
> options, latex_header.  Some of structures that might be used in latex
> like
> lstlisting and verbatim where the text also should not have
> flyspell-overlays.
>
> There are also some other places like label, caption and attr.
>

[-- Attachment #2: Type: text/html, Size: 2189 bytes --]

  reply	other threads:[~2012-07-29  8:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 20:14 More flyspell-overlays removed Bjarte Johansen
2012-07-28  9:27 ` Bastien
2012-07-28 22:38   ` Bjarte Johansen
2012-07-29  8:35     ` Jeffrey Spencer [this message]
2012-07-29 14:47       ` Bjarte Johansen
2012-07-30 11:03         ` Bastien
2012-07-30 11:13           ` Jeffrey Spencer
2012-07-30 11:44           ` Bjarte Johansen
2012-07-31 13:56             ` Jeffrey Spencer
2012-07-31 15:32             ` Bastien
2012-07-31 15:38               ` Bjarte Johansen
2012-07-31 16:33                 ` Bastien
2012-07-31 15:10         ` Sebastien Vauban
2012-07-31 15:32           ` Bastien
2012-08-07  3:57             ` Jeffrey Spencer
2012-08-07  9:18               ` Bastien
2012-08-07 11:40                 ` Jeffrey Spencer

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=CALmFPZ2hw4jE81C0bvX-xaumYQOxa-SKOjZsuXMNKeSxTXwtdA@mail.gmail.com \
    --to=jeffspencerd@gmail.com \
    --cc=bjo013@student.uib.no \
    --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).