From: Yasushi SHOJI <yashi@atmark-techno.com>
To: n.goaziou@gmail.com
Cc: bzg@altern.org, michael.ch.brand@gmail.com, emacs-orgmode@gnu.org
Subject: Re: link interfering with brackets when abbreviated
Date: Sun, 02 Mar 2014 09:22:32 +0900 [thread overview]
Message-ID: <87wqgdv48n.wl@dns1.atmark-techno.com> (raw)
In-Reply-To: <87ha7hpt6l.fsf@gmail.com>
Hi Nicolas,
Thanks for your time.
At Sat, 01 Mar 2014 21:20:18 +0100,
Nicolas Goaziou wrote:
>
> >> Anyway, I don't understand why there is so much fuss about this.
> >
> > That's because a) the commands have been working
>
> This is not a sufficient reason. We are discussing a minor feature.
> Removing it doesn't remove any functionality to Org, as the "thing" just
> saves a few keystrokes, on a good day.
Ok. If this is yet another bickshed, I'll drop from the discussion.
> While re-implementing the function, it appears that the feature just
> doesn't fit. So this is a good time to ponder about its real usefulness,
> and, if it is worth bending the new function to add it back. I think it
> isn't.
>
> As I already said, opening the next link in the same line is dubious. In
> the following example, with point between the links, the previous
> behaviour was to open "link2":
>
> [[link1]] [[link2]]
>
> Now consider the following case, where point is before the "a":
>
> [[link1]] a very ... very long line of text [[link2]]
>
> The previous behaviour implied to also open "link2". This is not
> really straightforward.
If the point is before the "a", that means the point is right after
the link, it should open `link1' instead of `link2', IMNSHO. This
isn't even the previous behavior, I admit, but if you move the pointer
to the end of the line (that's right after the link2), it _opened_
links2. This behavior works quite well with Emacs' cursor movement.
;; uga, `forward-word' doesn't work as I expected on
;; [[http://google.com][google]]. It stops at the first `o'.
> Worse, if `visual-line-mode' is on,
> [[link2]] can be many lines below. In the following case, with point
> still before the first "a", opening [[link2]] is just odd:
>
> [[link1]] a very ... very long line
> which spans over many visual lines
> of text [[link2]].
>
> It is odd because in the same situation, without `visual-line-mode' but
> with `auto-fill-mode' on, C-c C-o will report "No link found".
Both should report "No link found". `org-end-of-line' takes care of
`visual-line-mode', why not `org-open-at-link'?
--
yashi
next prev parent reply other threads:[~2014-03-02 0:22 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 12:11 link interfering with brackets when abbreviated Michael Brand
2014-02-26 15:10 ` Michael Brand
2014-02-26 15:25 ` Nicolas Goaziou
2014-02-26 15:44 ` Michael Brand
2014-02-26 15:54 ` Nicolas Goaziou
2014-02-26 16:22 ` Michael Brand
2014-02-26 16:41 ` Nicolas Goaziou
2014-02-26 17:03 ` Michael Brand
2014-02-26 17:20 ` Bastien
2014-02-26 19:02 ` Nicolas Goaziou
2014-02-26 22:54 ` Bastien
2014-02-27 10:28 ` Nicolas Goaziou
2014-02-27 11:04 ` Bastien
2014-02-27 20:01 ` Michael Brand
2014-02-27 22:08 ` Bastien
2014-02-27 23:43 ` Nicolas Goaziou
2014-03-01 18:44 ` Yasushi SHOJI
2014-03-01 20:20 ` Nicolas Goaziou
2014-03-01 20:54 ` Bastien
2014-03-01 20:57 ` Bastien
2014-03-01 21:35 ` Nicolas Goaziou
2014-03-01 21:50 ` Bastien
2014-03-01 22:14 ` Nicolas Goaziou
2014-03-02 13:35 ` Bastien
2014-03-03 14:12 ` Matt Lundin
2014-03-02 0:22 ` Yasushi SHOJI [this message]
2014-03-02 9:05 ` Nicolas Goaziou
2014-03-02 13:22 ` Bastien
2014-03-02 14:27 ` Nicolas Goaziou
2014-03-02 15:49 ` Bastien
2014-03-02 16:32 ` Thorsten Jolitz
2014-03-03 3:41 ` Josiah Schwab
2014-03-03 5:54 ` Michael Brand
2014-03-03 9:50 ` Context of interaction vs. literal syntactic interpretation (was: link interfering with brackets when abbreviated) Bastien
2014-03-03 16:09 ` Context of interaction vs. literal syntactic interpretation Matt Lundin
2014-03-03 18:00 ` Nick Dokos
2014-03-03 18:13 ` Jonathan Leech-Pepin
2014-03-14 13:46 ` Sebastien Vauban
2014-03-21 8:44 ` Bastien
2014-03-21 13:17 ` Nicolas Goaziou
2014-03-23 22:51 ` Bastien
2014-03-24 13:12 ` Nicolas Goaziou
2014-03-01 18:44 ` link interfering with brackets when abbreviated Yasushi SHOJI
2014-02-26 17:42 ` Bastien
2014-02-26 21:15 ` Nicolas Goaziou
2014-02-26 22:21 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2014-03-02 21:16 Gustav Wikström
2014-03-03 1:30 ` Ista Zahn
2014-03-03 19:33 ` Samuel Wales
2014-03-03 19:46 ` Samuel Wales
2014-03-03 22:18 ` Sebastien Vauban
2014-03-03 22:33 ` Samuel Wales
[not found] ` <CAJcAo8vh0F0tqgX4=gUhJoWFcAsTiwfyi7Fp=spQeoaBog1OMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-04 12:16 ` Sebastien Vauban
2014-03-04 20:06 ` Samuel Wales
2014-03-19 11:19 ` Bastien
2014-03-03 10:58 ` Christian Moe
2014-03-03 16:11 ` Sebastien Vauban
2014-03-03 23:16 ` Robert Horn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqgdv48n.wl@dns1.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@gmail.com \
--cc=n.goaziou@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.