From: brakjoller@hotmail.com (Barman Brakjoller)
Subject: Re: virtual space?
Date: 21 Oct 2003 01:47:57 -0700 [thread overview]
Message-ID: <1c58a7c3.0310210047.2e379e8b@posting.google.com> (raw)
In-Reply-To: wj0lb.4256$np1.3887@newsread3.news.pas.earthlink.net
> > Why would you want to move the cursor somewhere if you don't plan to
> > edit anything there?
>
> Having the cursor move to somewhere where I didn't tell it to go is
> annoying. For example, imagine holding down the up or down arrow key to
> move some distance in a file, like from the bottom of a window to somewhere
> in the middle. The cursor should move directly up the column it started in.
> But emacs doesn't do that.
I agree with you and I disagree with you:
1. I am annoyed with all people that answers "M-x picture-mode" to
this question all the time, when they clearly (yes, I really believe
that) see that in most cases picture-mode is not what the person
wants.
2. I understand that you are frustrated by the cursor jumping around,
I can see your point from a GUI/user experience point of view. But as
someone here said, are there any "real" benefits from this virtual
cursor? If there were I would expect that someone actually implemented
it in emacs. What do you want to *do* in that virtual place?
Hmm, come to think of it, I can actually find a valid use for it.
Imagine this text in a buffer:
blah blah blah
blah blah<-buffer ends here
If you have the buffer text above, it is *impossible* to copy a
rectangle with all the content of the buffer without needing to add
extra spaces at the end of the last line to get the cursor to the same
column as the third "blah" on the first line. Right? Having a virtual
cursor would solve the problem.
Anyway, this is no big problem for *me*.
/Mathias
next prev parent reply other threads:[~2003-10-21 8:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 21:31 virtual space? Michael Durland
2003-10-19 21:52 ` Sudarshan S. Chawathe
2003-10-19 23:25 ` Michael Durland
2003-10-20 5:36 ` Björn Lindström
2003-10-21 1:52 ` Michael Durland
2003-10-21 4:07 ` Dan Anderson
2003-10-21 5:44 ` Eli Zaretskii
2003-10-21 8:47 ` Barman Brakjoller [this message]
2003-10-21 15:04 ` Stefan Monnier
2003-10-22 1:33 ` Michael Durland
[not found] ` <mailman.2047.1066715377.21628.help-gnu-emacs@gnu.org>
2003-10-22 1:26 ` Michael Durland
2003-10-22 14:37 ` Eli Zaretskii
[not found] ` <mailman.2213.1066834114.21628.help-gnu-emacs@gnu.org>
2003-10-22 15:55 ` Kevin Rodgers
2003-10-22 17:44 ` Eli Zaretskii
[not found] ` <mailman.2225.1066844986.21628.help-gnu-emacs@gnu.org>
2003-12-02 21:09 ` Kai Grossjohann
2003-10-22 17:29 ` Stefan Monnier
2003-12-02 21:04 ` Kai Grossjohann
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=1c58a7c3.0310210047.2e379e8b@posting.google.com \
--to=brakjoller@hotmail.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.
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).