emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Josef Atmin <jatmin@web.de>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: "No link found" for <return> after <2016-02-21 Sun>
Date: Wed, 24 Feb 2016 13:09:04 +0100	[thread overview]
Message-ID: <20160224120904.GC25757@garlic> (raw)
In-Reply-To: <87io1e2x4n.fsf@nicolasgoaziou.fr>

Dear Nicolas,

that would be great.  Thanks for letting me know.

Josef.

On Wed, Feb 24, 2016 at 11:58:16AM +0100, Nicolas Goaziou wrote:
> Hello,
> 
> Josef Atmin <jatmin@web.de> writes:
> 
> > So there remains my wishlist item, namely that typing <return> after a
> > link results in a newline rather than activation of the link.  I would
> > find it much better if only a <return> on the link would activate it,
> > because I am often in the situation where I am at the end of a line
> > and I want to insert a newline, but because there is a link at the end
> > of the line right before the curser (not at the cursor), the link is
> > activated, which is mostly harmless but anoying.  To avoid that, I
> > have to either first tiype a <space> and then a <return> or first
> > Ctrl-o and then <right>.  But it is hard for me to always be aware of
> > the link and change my automatism of simply typing <return>.
> 
> AFAIR, this was also fixed in the same commit.
> 
> 
> Regards,
> 
> -- 
> Nicolas Goaziou

      reply	other threads:[~2016-02-24 12:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <145605054310.31999.11792052402300266373.reportbug@garlic.spices>
2016-02-23 22:13 ` "No link found" for <return> after <2016-02-21 Sun> Josef Atmin
2016-02-23 22:34   ` Nicolas Goaziou
2016-02-24  7:05     ` Josef Atmin
2016-02-24 10:58       ` Nicolas Goaziou
2016-02-24 12:09         ` Josef Atmin [this message]

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=20160224120904.GC25757@garlic \
    --to=jatmin@web.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).