From: Bernt Hansen <bernt@norang.ca>
To: emacs-orgmode@gnu.org
Subject: Re: SPC and BS behaviour changed in the agenda?
Date: Tue, 19 Feb 2013 13:25:20 -0500 [thread overview]
Message-ID: <871uccxisv.fsf@norang.ca> (raw)
In-Reply-To: <87ppzwgpj5.fsf@norang.ca> (Bernt Hansen's message of "Tue, 19 Feb 2013 12:51:58 -0500")
It turns out this is related to org-agenda-sticky set to t.
I'm just starting to play with sticky agendas and the scrolling
behaviour for SPC and BS changes for sticky agendas.
When I switch back to non-sticky agendas it works again.
I'll send an ECM tonight if this hasn't already been fixed by then :)
Regards,
Bernt
Bernt Hansen <bernt@norang.ca> writes:
> Please ignore this. There is some setting in my local emacs that is
> breaking this behaviour for me. It works fine with a minimal emacs on
> both my current commit and the tip of master.
>
> I should have checked first...
>
> Sorry for the noise.
>
> Bernt
>
> Bernt Hansen <bernt@norang.ca> writes:
>
>> Hi,
>>
>> I'm way behind the current tip of the master branch (Org-mode version
>> 7.9.3d (release_7.9.3d-899-g30ef38 @ /home/bernt/git/org-mode/lisp/))
>> but just noticed that SPACE and BACKSPACE behave differently now.
>>
>> Repeated SPACE used to scroll down the org file while BACKSPACE scrolls
>> up. I found this very convenient when browsing my org files for details
>> during my weekly review -- directly from my block agenda.
>>
>> I can achieve similar results with
>>
>> SPC C-M-v repeatedly but that is not nearly as convenient as tapping the
>> SPC key a few times. (and C-M-S-v to scroll up in the other window)
>>
>> I'll try and identify if this is still an issue on the current tip of
>> the master branch which commit changed this behaviour after I get home
>> tonight.
>>
>> Regards,
>> Bernt
next prev parent reply other threads:[~2013-02-19 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 15:31 SPC and BS behaviour changed in the agenda? Bernt Hansen
2013-02-19 17:51 ` Bernt Hansen
2013-02-19 18:25 ` Bernt Hansen [this message]
2013-02-19 18:39 ` Bastien
2013-02-19 19:22 ` Bernt Hansen
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=871uccxisv.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
/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).