From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Outline cycling does not preserve point's position
Date: Tue, 10 Sep 2013 18:33:16 +0200 [thread overview]
Message-ID: <87a9jk8wmr.fsf@gmail.com> (raw)
In-Reply-To: <20130910095043.GR20690@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Tue, 10 Sep 2013 11:50:43 +0200")
Hello,
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> On Tue, Sep 10, 2013 at 11:02:35AM +0200, Carsten Dominik wrote:
>>
>> On 10.9.2013, at 10:50, Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
>>
>> > On Tue, Sep 10, 2013 at 10:16:06AM +0200, Carsten Dominik wrote:
>> >>
>> >> The question is: What are people using C-arrow for?
>> >>
>> >> I think the main application is reasonably fast motion
>> >> and selection in a *linear* way. Is this correct, or do people
>> >> disagree here with me?
>> >
>> > I use it for navigating a buffer (not necessarily Org) linearly; i.e. go
>> > back and forth between parts I'm working on or to peruse the contents of
>> > a file. That said, often I feel the need for a navigation command which
>> > allows me to navigate the semantics of the buffer (which exactly what
>> > Nicolas's elements based navigation does).
>> >
>> >> The amazing element motion commands Nicolas has implement
>> >> correspond to sexp motion, as he has said himself.
>> >> Maybe C-M-f and C-M-b are the better binding match for these?
>> >
>> > I think you are right here. There is a need for both. For me, I use
>> > linear navigation more commonly; so I would prefer C-<up/down> for
>> > linear navigation and some other bindings (like C-M-f/b, as you suggest)
>> > for the elements based motion.
>>
>> And by linear, I think we don't mean strictly linear, but on a
>> paragraph/table/item scale, ignoring hierarchy.
>
> Yes. However I think I differ a bit on items. For me in a list like
> the following, I would call moving by paragraphs _within_ the list items
> linear; so, "Lorem..." → "Cras..." → "Integer..." → "Aenean..." →
> "Pellentesque...", and so on.
Here's a first draft for the linear forward motion. Disclaimer: I didn't
test it thoroughly.
(defun org-forward-linear-element ()
(interactive)
(when (eobp) (user-error "Cannot move further down"))
(let* ((origin (point))
(element (org-element-at-point))
(type (org-element-type element))
(contents-begin (org-element-property :contents-begin element))
(contents-end (org-element-property :contents-end element))
(end (let ((end (org-element-property :end element)) (parent element))
(while (and (setq parent (org-element-property :parent parent))
(= (org-element-property :contents-end parent) end))
(setq end (org-element-property :end parent)))
end)))
(skip-chars-forward " \r\t\n")
(or (eobp) (goto-char (max (line-beginning-position) origin)))
(cond ((or (eobp) (= (point) end)))
((not contents-begin) (goto-char end))
((< (point) contents-begin)
(cond ((eq type 'item)
(end-of-line)
(org-forward-and-down-element))
((eq type 'table-row) (goto-char end))
(t (goto-char contents-begin))))
((>= (point) contents-end) (goto-char end))
((eq type 'paragraph) (goto-char end))
((eq type 'plain-list)
(end-of-line)
(org-forward-and-down-element))
((eq type 'table)
(forward-line)
(when (>= (point) contents-end) (goto-char end)))
((eq type 'verse-block)
(or (re-search-forward "^[ \t]*$" contents-end t)
(goto-char end)))
(t (error "This shouldn't happen")))
(when (org-invisible-p2) (goto-char end))))
WDYT?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-09-10 16:33 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 12:11 Outline cycling does not preserve point's position Sebastien Vauban
2013-09-07 14:17 ` Carsten Dominik
[not found] ` <BED1FBAA-8BB5-45D6-8328-11C0BB2DF015-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-07 19:28 ` Sebastien Vauban
2013-09-08 6:16 ` Carsten Dominik
2013-09-09 7:57 ` Sebastien Vauban
2013-09-08 11:03 ` Eric Schulte
2013-09-09 8:39 ` Sebastien Vauban
2013-09-08 16:23 ` Carsten Dominik
2013-09-09 8:11 ` Sebastien Vauban
2013-09-09 8:13 ` Carsten Dominik
2013-09-09 8:23 ` Sebastien Vauban
2013-09-09 8:27 ` Carsten Dominik
2013-09-09 8:33 ` Sebastien Vauban
2013-09-09 8:38 ` Bastien
2013-09-09 9:05 ` Carsten Dominik
2013-09-09 11:32 ` Nicolas Goaziou
2013-09-09 11:49 ` Bastien
2013-09-09 15:27 ` Nicolas Goaziou
2013-09-09 14:23 ` Carsten Dominik
2013-09-09 15:16 ` Jambunathan K
2013-09-09 15:41 ` Nicolas Goaziou
2013-09-09 17:42 ` Sebastien Vauban
2013-09-10 3:47 ` Carsten Dominik
2013-09-10 6:03 ` Carsten Dominik
2013-09-10 6:48 ` Eric Abrahamsen
2013-09-10 7:32 ` Suvayu Ali
2013-09-10 7:53 ` Suvayu Ali
2013-09-10 7:58 ` Carsten Dominik
2013-09-10 8:16 ` Carsten Dominik
2013-09-10 8:50 ` Suvayu Ali
2013-09-10 9:02 ` Carsten Dominik
2013-09-10 9:50 ` Suvayu Ali
2013-09-10 16:33 ` Nicolas Goaziou [this message]
2013-09-10 18:35 ` Jambunathan K
2013-09-10 18:39 ` Nicolas Goaziou
2013-09-10 19:22 ` Jambunathan K
2013-09-10 19:40 ` Jambunathan K
2013-09-10 19:52 ` Nicolas Goaziou
2013-09-10 18:58 ` Suvayu Ali
2013-09-10 19:07 ` Suvayu Ali
2013-09-10 19:48 ` Nicolas Goaziou
2013-09-10 20:13 ` Suvayu Ali
2013-09-10 20:29 ` Nicolas Goaziou
2013-09-10 21:08 ` Carsten Dominik
2013-09-11 12:24 ` Suvayu Ali
2013-09-12 6:54 ` Jambunathan K
2013-09-12 9:11 ` Nicolas Goaziou
2013-09-12 9:28 ` Jambunathan K
2013-09-12 9:47 ` Suvayu Ali
2013-09-11 2:49 ` Jambunathan K
2013-09-11 11:09 ` Nicolas Goaziou
2013-09-11 11:34 ` Jambunathan K
2013-09-11 15:19 ` Nicolas Goaziou
2013-09-11 15:40 ` Jambunathan K
2013-09-11 15:31 ` Jambunathan K
2013-09-11 15:40 ` Nicolas Goaziou
2013-09-11 16:14 ` Jambunathan K
2013-09-11 20:01 ` Nicolas Goaziou
2013-09-11 22:11 ` Suvayu Ali
2013-09-12 6:43 ` Jambunathan K
2013-09-12 9:07 ` Nicolas Goaziou
2013-09-12 10:12 ` Jambunathan K
2013-09-12 7:17 ` Sebastien Vauban
2013-09-13 10:57 ` Carsten Dominik
2013-09-13 22:29 ` Nicolas Goaziou
2013-09-14 5:33 ` Carsten Dominik
2013-09-14 17:16 ` Suvayu Ali
2013-09-15 4:39 ` Carsten Dominik
2013-09-10 20:16 ` Samuel Wales
2013-09-10 5:06 ` Jambunathan K
2013-09-11 3:57 ` Jambunathan K
2013-09-11 15:47 ` Nicolas Goaziou
2013-09-09 8:38 ` Carsten Dominik
2013-09-09 11:30 ` Nicolas Goaziou
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=87a9jk8wmr.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@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 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).