Nicolas Goaziou n.goaz...@gmail.com writes:
Should there be a pit-stop at #+END in the segment below.
You can use `org-forward-element' to go there.
It makes no difference if I use `org-forward-element' or
`org-forward-linear-element'. The reason is clear if one examines the
parser output.
Hi Nicolas,
On Sat, Sep 14, 2013 at 12:29:00AM +0200, Nicolas Goaziou wrote:
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
When the functions are done, please go ahead and commit them and bind
them to C-up/down.
Done.
Do you think it would be nicer if
On 14.9.2013, at 19:16, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
Hi Nicolas,
On Sat, Sep 14, 2013 at 12:29:00AM +0200, Nicolas Goaziou wrote:
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
When the functions are done, please go ahead and commit them and bind
them to
Hi Nicolas,
thanks for these. Please see the two comments below.
On Sep 11, 2013, at 10:01 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Jambunathan K kjambunat...@gmail.com writes:
I am happy with whatever is the latest version. You may want to commit
it.
I copy here[fn:1] the
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
When the functions are done, please go ahead and commit them and bind
them to C-up/down.
Done.
Regards,
--
Nicolas Goaziou
Hello Nicolas,
thank you!
- Carsten
On 14.9.2013, at 00:29, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
When the functions are done, please go ahead and commit them and bind
them to C-up/down.
Done.
Regards,
--
Hello Nicolas,
Nicolas Goaziou wrote:
Some points are still to be discussed:
1. What to do on node properties?
I would opt for `forward-paragraph', to have something different than
`next-line'. Otherwise, `C-down' and `down' would simply do the same thing.
Not forbidden, but seems
Hello,
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Some points are still to be discussed:
1. What to do on node properties?
2. What to do on source blocks?
Looks good to me.
Should there be a pit-stop at #+END in the segment below.
Jambunathan K kjambunat...@gmail.com writes:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
And I agree with you, beginning of line is a good target column.
On reading Nicolas's explanation, I agree too. This is better.
The decision should be based on what the user would do after doing a
Hi Jambu,
On Thu, Sep 12, 2013 at 02:58:02PM +0530, Jambunathan K wrote:
Nicolas Goaziou n.goaz...@gmail.com writes:
Jambunathan K kjambunat...@gmail.com writes:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
And I agree with you, beginning of line is a good target column.
On
Nicolas Goaziou n.goaz...@gmail.com writes:
I don't understand. Are you talking about the error message? There is no
canonical C-down position, so I'm a bit confused.
Put your cursor on the blank line between. Do a C-down. You will see
the cursor moving and also an error reported. So, the
Nicolas Goaziou n.goaz...@gmail.com writes:
Thanks. Take 2:
Looks good. Less surprises. Some open questions... I have no
preference one way or the other.
1. Seems to like beginning of line. May be it should do a
back-to-indentation. It is disconcerting to have cursor rest on
Nicolas Goaziou n.goaz...@gmail.com writes:
Here's a first draft for the linear forward motion.
cond: Symbol's function definition is void: org-forward-and-down-element
I will try out your changes later in the day...
Meanwhile,
I don't know what pre-order means. What about
`org-flat-forward-element'
By, flat or linear you really mean a serialized (or stringified) version
of parse-tree. i.e., An Org buffer is really a serialized
representation of the parse
Jambunathan K kjambunat...@gmail.com writes:
Seems to like beginning of line.
For repated C-down motion, where the cursor rests within the element
is immaterial. So the question is at what position the cursor should
rest so that whatever becomes easy.
Whatever could be:
1. editing.
2.
Some suggestions:
1. Give a better name. Say pre-order traversal of element in the
parse tree. [1]
2. Now if I
M-h, C-x C-x and Deactivate mark,
I essentially short-circuit the traversal of whole subtree rooted at
point. There should be a convenient binding for it. Same
I am happy with whatever is the latest version. You may want to commit
it.
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
And I agree with you, beginning of line is a good target column.
On reading Nicolas's explanation, I agree too. This is better.
The decision should be based on what the user would do after doing a
C-down and C-up.
If *you* use C-down and C-up
Nicolas Goaziou n.goaz...@gmail.com writes:
`org-forward-paragraph' is much better. As long as the docstring or
comments mention that Org's notion of paragraph is much more nuanced or
richer than a text-mode's notion of paragraph.
OK. Suggestions welcome.
Meanwhile, here is an updated
Nicolas Goaziou n.goaz...@gmail.com writes:
Some points are still to be discussed:
1. What to do on node properties?
2. What to do on source blocks?
Looks good to me.
Should there be a pit-stop at #+END in the segment below.
--8---cut
Nicolas Goaziou n.goaz...@gmail.com writes:
It's a Sexp motion.
Good opportunity to review the following bindings.
C-c C-^ org-up-element
C-c C-_ org-down-element
Btw, C-M-p and C-M-n actually traverses the
Nicolas Goaziou n.goaz...@gmail.com writes:
Jambunathan K kjambunat...@gmail.com writes:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
And I agree with you, beginning of line is a good target column.
On reading Nicolas's explanation, I agree too. This is better.
The decision should be
Hello,
Jambunathan K kjambunat...@gmail.com writes:
Some suggestions:
1. Give a better name. Say pre-order traversal of element in the
parse tree. [1]
I don't know what pre-order means. What about
`org-flat-forward-element' or simply (but misleading) `org-forward-paragraph'?
3. When
On Tue, Sep 10, 2013 at 11:08:23PM +0200, Carsten Dominik wrote:
And I agree with you, beginning of line is a good target column.
On reading Nicolas's explanation, I agree too. This is better.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Jambunathan K kjambunat...@gmail.com writes:
`org-forward-paragraph' is much better. As long as the docstring or
comments mention that Org's notion of paragraph is much more nuanced or
richer than a text-mode's notion of paragraph.
OK. Suggestions welcome.
Meanwhile, here is an updated
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
I don't understand. Are you talking about the error message? There is no
canonical C-down position, so I'm a bit confused.
Put your cursor on the blank line between. Do a C-down. You will see
the
Jambunathan K kjambunat...@gmail.com writes:
Hmmm... Object traversal.
Now there should be a way to move between objects: Move to the next
object of the same type the cursor is on.
This is interesting but not really possible at the moment. Currently
Elements implement successors
Jambunathan K kjambunat...@gmail.com writes:
I am happy with whatever is the latest version. You may want to commit
it.
I copy here[fn:1] the current version, for the record, along with its backward
counterpart. Some points are still to be discussed:
1. What to do on node properties?
2.
Hi Nicolas,
On Wed, Sep 11, 2013 at 10:01:31PM +0200, Nicolas Goaziou wrote:
Jambunathan K kjambunat...@gmail.com writes:
I am happy with whatever is the latest version. You may want to commit
it.
I copy here[fn:1] the current version, for the record, along with its backward
On 10.9.2013, at 05:47, Carsten Dominik carsten.domi...@gmail.com wrote:
On 9.9.2013, at 17:41, Nicolas Goaziou n.goaz...@gmail.com wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
It is extremely predictable if you know about the structure of an Org
document and if you think
Carsten Dominik carsten.domi...@gmail.com writes:
On 10.9.2013, at 05:47, Carsten Dominik carsten.domi...@gmail.com wrote:
On 9.9.2013, at 17:41, Nicolas Goaziou n.goaz...@gmail.com wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
It is extremely predictable if you know about
On Tue, Sep 10, 2013 at 08:03:32AM +0200, Carsten Dominik wrote:
One more thought: What if the paragraph motion commands did use elements, but
ignored the hierarchy. So they jump to the next headline, paragraph, table,
src block, item?
I think this would feel similar to what paragraph
On Tue, Sep 10, 2013 at 09:32:57AM +0200, Suvayu Ali wrote:
On Tue, Sep 10, 2013 at 08:03:32AM +0200, Carsten Dominik wrote:
One more thought: What if the paragraph motion commands did use elements,
but
ignored the hierarchy. So they jump to the next headline, paragraph,
table, src
On 10.9.2013, at 09:53, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
On Tue, Sep 10, 2013 at 09:32:57AM +0200, Suvayu Ali wrote:
On Tue, Sep 10, 2013 at 08:03:32AM +0200, Carsten Dominik wrote:
One more thought: What if the paragraph motion commands did use elements,
but
ignored the
On 10.9.2013, at 09:58, Carsten Dominik carsten.domi...@gmail.com wrote:
On 10.9.2013, at 09:53, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
On Tue, Sep 10, 2013 at 09:32:57AM +0200, Suvayu Ali wrote:
On Tue, Sep 10, 2013 at 08:03:32AM +0200, Carsten Dominik wrote:
One more thought:
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
On 10.9.2013, at 10:50, Suvayu Ali fatkasuvayu+li...@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
On Tue, Sep 10, 2013 at 11:02:35AM +0200, Carsten Dominik wrote:
On 10.9.2013, at 10:50, Suvayu Ali fatkasuvayu+li...@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
Nicolas Goaziou n.goaz...@gmail.com writes:
When depth isn't involved
When I am within a nested list (any arbitray position) and I C-down what
should happen?
When I am on an headline and I C-down, I find it disconcerting that
Hello,
Suvayu Ali fatkasuvayu+li...@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+li...@gmail.com wrote:
On Tue, Sep 10, 2013 at 10:16:06AM +0200, Carsten Dominik wrote:
The question is: What are
Hi Nicolas,
On Tue, Sep 10, 2013 at 09:48:53PM +0200, Nicolas Goaziou wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
1. When traversing the file header, goes one line at a time. I would
expect to go to the next blank line. In the attached Org file, from
somewhere on
Hello,
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
1. When traversing the file header, goes one line at a time. I would
expect to go to the next blank line. In the attached Org file, from
somewhere on #+TITLE to the blank line before the first headline.
There no such thing as a
On Tue, Sep 10, 2013 at 08:58:43PM +0200, Suvayu Ali wrote:
Some comments and a backtrace (I used the corrected 2nd revision):
Forgot to edit that out, no backtrace. :)
--
Suvayu
Open source is the future. It sets us free.
Hello,
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Here's a first draft for the linear forward motion.
cond: Symbol's function definition is void:
org-forward-and-down-element
Hmm. That's a silly mistake (few aren't): I changed its name as a
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Thanks. Take 2:
Looks good. Less surprises. Some open questions... I have no
preference one way or the other.
1. Seems to like beginning of line. May be it should do a
back-to-indentation. It
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Okay agreed there is nothing called file header, but would be nice to
skip all the setup stuff (wherever in the file) and get to the
content.
It's really out of the scope of this function. There are other solutions
to ignore large file headers,
On 10.9.2013, at 21:48, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
1. When traversing the file header, goes one line at a time. I would
expect to go to the next blank line. In the attached Org file, from
somewhere on #+TITLE to
Hi Carsten,
Carsten Dominik wrote:
On 7.9.2013, at 21:28, Sebastien Vauban sva-n...@mygooglest.com wrote:
Carsten Dominik wrote:
On 7.9.2013, at 14:11, Sebastien Vauban sva-n...@mygooglest.com wrote:
Since a little while, I've observed that point's position is not anymore
preserved when
Hi Carsten,
Carsten Dominik wrote:
- not possible anymore to use C-a or C-e in code blocks to select regions;
not reported yet, though I reported similar problems with C-arrows
(apparently due to a change which is now officially part of 8.1). IMO,
that renders editing of code block in
On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote:
Hi Carsten,
Carsten Dominik wrote:
- not possible anymore to use C-a or C-e in code blocks to select regions;
not reported yet, though I reported similar problems with C-arrows
(apparently due to a change which is
Hi Carsten,
Carsten Dominik wrote:
On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote:
Carsten Dominik wrote:
- not possible anymore to use C-a or C-e in code blocks to select regions;
not reported yet, though I reported similar problems with C-arrows
(apparently due to
On 9.9.2013, at 10:23, Sebastien Vauban sva-n...@mygooglest.com wrote:
Hi Carsten,
Carsten Dominik wrote:
On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote:
Carsten Dominik wrote:
- not possible anymore to use C-a or C-e in code blocks to select regions;
not reported
Hi Carsten,
Carsten Dominik wrote:
On 9.9.2013, at 10:23, Sebastien Vauban sva-n...@mygooglest.com wrote:
Carsten Dominik wrote:
On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote:
Carsten Dominik wrote:
- not possible anymore to use C-a or C-e in code blocks to select
Hi Sébastien,
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
Of course, the nicest would be to have both: the current `C-down' for text,
and the programmatic behavior when _in code blocks_. Maybe, that's not
possible, though...
We could have org-ctrldown and
On 9.9.2013, at 10:33, Sebastien Vauban sva-n...@mygooglest.com wrote:
Hi Carsten,
Carsten Dominik wrote:
On 9.9.2013, at 10:23, Sebastien Vauban sva-n...@mygooglest.com wrote:
Carsten Dominik wrote:
On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote:
Carsten Dominik
Hi Eric,
Eric Schulte wrote:
not possible anymore to cut a code snippet in two parts with C-c C-v C-d
(demarcate block); already reported (without bisect), no answer;
This works for me, could you report a minimal recipe for reproduction, and
maybe a git bisect commit?
This does work again
On 9.9.2013, at 10:38, Bastien b...@gnu.org wrote:
Hi Sébastien,
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
Of course, the nicest would be to have both: the current `C-down' for text,
and the programmatic behavior when _in code blocks_. Maybe, that's
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
On 9.9.2013, at 10:38, Bastien b...@gnu.org wrote:
We could have org-ctrldown and friends the same way we have org-shift*
commands. org-ctrldown would use `org-forward-element' when on some
Org element, and `forward-paragraph'
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
This might be difficult, but not impossible.
I think this might be a question for Nicolas to answer?
It boils down to something like:
(if (eq (org-element-type (org-element-at-point)) 'src-block)
;; Do forward-paragraph
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
We could have org-ctrldown and friends the same way we have org-shift*
commands. org-ctrldown would use `org-forward-element' when on some
Org element, and `forward-paragraph' elsewhere.
elsewhere doesn't make sense here since point
On 9.9.2013, at 13:32, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
On 9.9.2013, at 10:38, Bastien b...@gnu.org wrote:
We could have org-ctrldown and friends the same way we have org-shift*
commands. org-ctrldown would use
It is extremely predictable if you know about the structure of an Org
document and if you think in elements.
Move over the smart navigation to C-M-f and friends.
(info (emacs) Expressions)
Programmers among us can exploit it.
Hello,
Bastien b...@gnu.org writes:
But you got the idea: use `org-forward-element' when moving
within structural elements of various kinds make sense and use
`forward-paragraph' otherwise.
No, I still don't get the idea, really.
It is predictable, but sometimes counter-intuitive: for
Carsten Dominik carsten.domi...@gmail.com writes:
It is extremely predictable if you know about the structure of an Org
document and if you think in elements.
It's a Sexp motion.
It is unexpected for a user who is used to C-arrow doing paragraph
motion. In Org, org-backward-element climbs
Hello Nicolas,
Nicolas Goaziou wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
It is extremely predictable if you know about the structure of an Org
document and if you think in elements.
It's a Sexp motion.
It is unexpected for a user who is used to C-arrow doing paragraph
On 9.9.2013, at 17:41, Nicolas Goaziou n.goaz...@gmail.com wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
It is extremely predictable if you know about the structure of an Org
document and if you think in elements.
It's a Sexp motion.
It is unexpected for a user who is used
Hi Sebastien,
On 7.9.2013, at 21:28, Sebastien Vauban sva-n...@mygooglest.com wrote:
Hi Carsten,
Carsten Dominik wrote:
On 7.9.2013, at 14:11, Sebastien Vauban sva-n...@mygooglest.com wrote:
Since a little while, I've observed that point's position is not anymore
preserved when cycling
Not yet. I have many Chinese plates turning at the moment, but I'll try to do
that very soon. And I have other problems to report or bisect:
- not possible anymore to cut a code snippet in two parts with C-c C-v C-d
(demarcate block); already reported (without bisect), no answer;
This
On 7.9.2013, at 21:28, Sebastien Vauban sva-n...@mygooglest.com wrote:
Hi Carsten,
Carsten Dominik wrote:
On 7.9.2013, at 14:11, Sebastien Vauban sva-n...@mygooglest.com wrote:
Since a little while, I've observed that point's position is not anymore
preserved when cycling buffer's view
Hello,
Since a little while, I've observed that point's position is not anymore
preserved when cycling buffer's view with S-TAB.
Sometimes, point stays where it was (even when in the body of entries);
sometimes, not.
See http://screencast.com/t/1sr6Lezk:
- when on the first letter of From, in
Hi Sebastien,
you say since a little while. Have you tried to bisect?
Or has it been like this always?
Also, I am not convinced that staying in invisible places is the
right behavior at all. Even though I would agree that three S-TAB
in a row should be a null operation.
May be it would be
Hi Carsten,
Carsten Dominik wrote:
On 7.9.2013, at 14:11, Sebastien Vauban sva-n...@mygooglest.com wrote:
Since a little while, I've observed that point's position is not anymore
preserved when cycling buffer's view with S-TAB.
Sometimes, point stays where it was (even when in the body of
72 matches
Mail list logo
