From: jidanni@jidanni.org
To: 373@emacsbugs.donarmstrong.com
Subject: bug#373: scroll-up, scroll-down don't respect current column
Date: Mon, 09 Jun 2008 12:39:50 +0800 [thread overview]
Message-ID: <87iqwjgr1l.fsf@jidanni.org> (raw)
In-Reply-To: 86iqwjitwz.fsf@macs.hw.ac.uk
Maybe all this should be related to if 'truncate long lines' is
enabled, or if there is the danger that Joe Wells mentioned on the
current line(s). Anyway "why a prejudice for column 0 if column 23 was
where we were". If the column we want doesn't exist on the current
line, temporarily go the nearest column to it.
next prev parent reply other threads:[~2008-06-09 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12770.1212765753.18990.bug-gnu-emacs@gnu.org>
2008-06-08 19:54 ` bug#373: scroll-up, scroll-down don't respect current column Joe Wells
2008-06-09 4:39 ` jidanni [this message]
[not found] <handler.373.D373.121276843021631.notifdone@emacsbugs.donarmstrong.com>
2008-06-06 17:28 ` jidanni
2008-06-05 23:38 jidanni
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iqwjgr1l.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=373@emacsbugs.donarmstrong.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.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).