emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Leo <sdl.web@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Right click on link bug
Date: Sun, 18 Mar 2007 21:46:54 +0000	[thread overview]
Message-ID: <m2vegyp6lt.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: <b6226de362b8a74cee92be9ea85f28b1@science.uva.nl> (Carsten Dominik's message of "Sun\, 18 Mar 2007 21\:40\:01 +0100")

On 2007-03-18, Carsten Dominik said:

> On Mar 16, 2007, at 18:38, Leo wrote:
>
>> Dear all,
>>
>> Put the following line in a buffer:
>>   [[http://www.google.com][Musick is wrong]]
>>
>> then enable org-mode and flyspell-mode. Now right click on the word
>> "Musick" and you can see the behavior of mouse1 has be changed to yank
>> instead of opening the link.
>
> That will teach you!
> Don't misspell your links!!!!!  :-)
>
>
> Well, competing overlays with competing keymaps, I  really would
> not know how to fix this on my side.  I know that ispell (and
> therefore flyspell) has some ways to not check TeX command names,
> for example.  But I am not sure if this is extensible so that
> we could use it for org-mode, making it skip links.  And I am
> not even sure if this is what you would want, because it is
> actually nice to have the description part of a link spell-checked!
>
> Summary:
>
> If you use flyspell, do actually use it to correct your typos :-)
>
> Cheers.
>
> - Carsten

For example, if I have an internal link [[* MFE][MFE]], mouse1 won't
bring it to the right place. This is when it is rather inconvenient.

-- 
Leo <sdl.web AT gmail.com>                         (GPG Key: 9283AA3F)

  reply	other threads:[~2007-03-18 21:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 17:38 Right click on link bug Leo
2007-03-18 20:40 ` Carsten Dominik
2007-03-18 21:46   ` Leo [this message]
2007-03-18 22:55     ` Carsten Dominik
2007-03-20 12:52       ` Leo
2007-03-20 16:18         ` Carsten Dominik
2007-03-20 17:52           ` Leo
2007-03-21  9:33           ` Leo
2007-03-21  9:53             ` Carsten Dominik
2007-03-21 10:13               ` Leo

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=m2vegyp6lt.fsf@sl392.st-edmunds.cam.ac.uk \
    --to=sdl.web@gmail.com \
    --cc=dominik@science.uva.nl \
    --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).