On Aug 26, 2009, at 8:22 AM, Bastien wrote:
Carsten Dominik writes:
1. n/p remain as they where
2. Moving forward/backward though time will be `f' and `b'
3. Follow mode goes to the "F" key, a capital letter does
make sense here given that some other modes like [G]rid
and clock[R]eport a
On Aug 27, 2009, at 3:05 AM, Samuel Wales wrote:
Looks good. However, you might want to have cursor movement work, if
the keys will not be functional, so that people can mark text (nobody
mentioned that yet). Did you get a chance to look at my proposal for
right and left arrow keys?
Yes, I
On 27 Aug 2009, at 06:47, Charles Philip Chan wrote:
Carsten Dominik writes:
[snip]
5. The cursor keys and are remapped to a
function that does nothing, except showing a message
that you should now use f/b to move through time.
Looks good, but like others have said, I prefer the an
Carsten Dominik writes:
> 1. n/p remain as they where
> 2. Moving forward/backward though time will be `f' and `b'
> 3. Follow mode goes to the "F" key, a capital letter does
>make sense here given that some other modes like [G]rid
>and clock[R]eport and [D]iary are on capitals as well.
>
YES for both
I fell often in this trap too.
2009/8/25 Rainer Stengele
> Carsten Dominik schrieb:
> > Hi,
> >
> > we have the proposal to do the following key changes in the agenda:
> >
> > 1. Make the cursor keys LEFT and RIGHT do normal cursor motion again
> > 2. Use the keys "n" and "p" to sw
Looks good. However, you might want to have cursor movement work, if
the keys will not be functional, so that people can mark text (nobody
mentioned that yet). Did you get a chance to look at my proposal for
right and left arrow keys?
--
Myalgic encephalomyelitis causes death (Jason et al. 2006
Carsten Dominik writes:
> 1. n/p remain as they where
> 2. Moving forward/backward though time will be `f' and `b'
> 3. Follow mode goes to the "F" key, a capital letter does
>make sense here given that some other modes like [G]rid
>and clock[R]eport and [D]iary are on capitals as well.
>
On Aug 25, 2009, at 5:31 PM, Manish wrote:
On Tue, Aug 25, 2009 at 8:38 PM, Christian Egli wrote:
Carsten Dominik writes:
we have the proposal to do the following key changes in the agenda:
1. Make the cursor keys LEFT and RIGHT do normal cursor motion again
No. Why would you want to do c
On Aug 25, 2009, at 5:08 PM, Christian Egli wrote:
Carsten Dominik writes:
we have the proposal to do the following key changes in the agenda:
1. Make the cursor keys LEFT and RIGHT do normal cursor motion again
No. Why would you want to do cursor motion in the agenda?
There is not good
On Tue, Aug 25, 2009 at 11:31, Manish wrote:
> On Tue, Aug 25, 2009 at 8:38 PM, Christian Egli wrote:
>> No. Why would you want to do cursor motion in the agenda?
>
> One could make part of a heading a link to, say, an email, and may want to
> visit that.
Clockreport also shows links which can be
On Tue, Aug 25, 2009 at 8:38 PM, Christian Egli wrote:
> Carsten Dominik writes:
>
>> we have the proposal to do the following key changes in the agenda:
>>
>> 1. Make the cursor keys LEFT and RIGHT do normal cursor motion again
>
> No. Why would you want to do cursor motion in the agenda?
One cou
Chris Leyon writes:
> Another solution would be to use "f" and "b" to move forward and
> backward in time. Some other Agenda bindings would have to change to
> accommodate this. Old "f" (org-agenda-follow-mode) could become "F"
> which is unused. But "b" and "B" are both used and would need to
Benjamin Andresen writes:
> As Leo wrote: ibuffer, gnus, dired & others all use 'n' for next
> line and 'p' for previous line.
>
> And with the recent mark and unmark feature inspired by dired, doing
> what it does, seems intuitive as far as emacs goes.
Fair enough.
I would favor the `f/b' ke
> all use 'n' for next line and 'p' for previous line.
I think the modes that use 'n' for next line and 'p' for next/previous
line tend to be 'single page' modes (e.g., dired). I personally
rarely use n/p even in those: C-n/C-p are automatic in my fingers and
they always work so that I do not n
On Aug 25, 2009, at 2:20 PM, Chris Leyon wrote:
Another solution would be to use "f" and "b" to move forward and
backward in time. Some other Agenda bindings would have to change to
accommodate this. Old "f" (org-agenda-follow-mode) could become "F"
which is unused. But "b" and "B" are both
Another solution would be to use "f" and "b" to move forward and
backward in time. Some other Agenda bindings would have to change to
accommodate this. Old "f" (org-agenda-follow-mode) could become "F"
which is unused. But "b" and "B" are both used and would need to be
remapped.
Obviously this
Hi everyone,
I tend to agree with the arguments that "n" and "p" should move
vertically in the agenda buffer, because many Emacs modes do
it like this.
So it seem to me that this discussion should focus on which keys should
move the agenda forward and backward in time.
- Carsten
On Aug 25, 200
Benjamin Andresen writes:
> Carsten Dominik writes:
>
>> Hi,
>>
>> we have the proposal to do the following key changes in the agenda:
>>
>> 1. Make the cursor keys LEFT and RIGHT do normal cursor motion again
>> 2. Use the keys "n" and "p" to switch the agenda to earlier
>>and later dates.
18 matches
Mail list logo
