From: Peter Tury <tury.peter@gmail.com>
Subject: Re: next-line + recenter (- redraw frame)?
Date: Mon, 06 Mar 2006 08:36:28 GMT [thread overview]
Message-ID: <19aniuq151di2$.1qyujo75j1w3b$.dlg@40tude.net> (raw)
In-Reply-To: mailman.1.1141424503.26251.help-gnu-emacs@gnu.org
On Fri, 3 Mar 2006 23:20:55 +0100, Peter Dyballa wrote:
> Please compare it to scroll-down-in-place in lisp/term/sun.el by Jeff
> Peck!
>
> (defun scroll-down-in-place (n)
> (interactive "p")
> (previous-line n)
> (scroll-down n))
>
> (defun scroll-up-in-place (n)
> (interactive "p")
> (next-line n)
> (scroll-up n))
Hi,
thanks for the info! This is again really almost the same as I wanted.
(Recenter is not so important, maybe scroll- is better.) However this has a
"big" disadvantage: it forgets the correct column always. The problem is in
next-line (more exactly: line-move-1) as I mentioned earlier, I know...
What do you think: is it realistic to modify simple.el "officially" to
eliminate this "bug"? I think we would have a variable
column-keeping-line-moves-list or something similar what would tell what
commands should be treated as now next-line and previous-line. Its default
could be '(next-line previous-line), so we would have backword
compatibility.
After this, if the user adds e.g. scroll-up-in-place to this list, then
scroll-up-in-place would work "correctly" in the above form. (I can imagine
this is not the required functionality for scroll-up-in-place, but it is
just an example here).
What should I do if I want to propose this "officially"? I see that
simple.el's maintainer is FSF...
Br,
P
next prev parent reply other threads:[~2006-03-06 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 16:54 next-line + recenter (- redraw frame)? Peter Tury
2006-03-03 17:36 ` Ralf Angeli
2006-03-06 8:17 ` Peter Tury
2006-03-06 8:43 ` Ralf Angeli
2006-03-06 9:34 ` Peter Tury
2006-03-03 22:20 ` Peter Dyballa
[not found] ` <mailman.1.1141424503.26251.help-gnu-emacs@gnu.org>
2006-03-06 8:36 ` Peter Tury [this message]
2006-03-26 2:38 ` David Combs
2006-03-26 10:10 ` Peter Dyballa
2006-03-27 15:51 ` Kevin Rodgers
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='19aniuq151di2$.1qyujo75j1w3b$.dlg@40tude.net' \
--to=tury.peter@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.