From: Carsten Dominik <dominik@science.uva.nl>
To: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Two bugs
Date: Wed, 30 May 2007 17:24:43 +0200 [thread overview]
Message-ID: <9d6b6efbd81deb17ae0ac5b47ed4c2b8@science.uva.nl> (raw)
In-Reply-To: <m28xb6fk02.fsf@sl392.st-edmunds.cam.ac.uk>
On May 30, 2007, at 16:45, Leo wrote:
> Dear Carsen,
>
> 1. unnecessary point movement
>
> When 'S-tab' (visibility cycling), the `point' (cursor) will be moved
> to
> the first headline, which will be a surprise to users. I think the
> movement should be kept as minimal as possible i.e. it should be kept
> within the tree the `point' is originally in.
>
> This annoyance becomes noticeable when the file is big such as when
> using a single .org file for GTD.
This is clearly a matter of taste. Certainly the cursor
should be moved to a visible location, would you agree?
The motivation for the current behavior is: If you switch
to overview mode, you probably want to see as much of the file
as possible, so my instinct was to put it back to the first heading.
But maybe you are right that this is not good if there are
many screens full of top level headings......
>
> 2. inconsistent key binding definitions
>
> There are only a few places where the key bindings are defined by
> `define-key' and the rest are done by `org-defkey'.
>
> Can those define-key be replaced by org-defkey?
There are exactly 2 (not counting removing the outline menus...)
(define-key org-mode-map (kbd "<backtab>") 'org-shifttab)
(define-key org-mode-map "\C-a" 'org-beginning-of-line)
The second replaces the beginning-of-line comment, my feeling was
that this one should not go through org-defkey. The first one I did
fix now.
- Carsten
next prev parent reply other threads:[~2007-05-30 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 14:45 Two bugs Leo
2007-05-30 15:24 ` Carsten Dominik [this message]
2007-05-31 0:26 ` Leo
2007-05-31 14:39 ` Carsten Dominik
2007-05-31 14:47 ` Leo
2007-05-31 17:05 ` Carsten Dominik
2007-05-31 17:43 ` Leo
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=9d6b6efbd81deb17ae0ac5b47ed4c2b8@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=sdl.web@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).