From: Tassilo Horn <tassilo@member.fsf.org>
To: help-gnu-emacs@gnu.org
Subject: Re: line-move-visual?
Date: Thu, 23 Oct 2008 12:46:18 +0200 [thread overview]
Message-ID: <87ljwf1tdx.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: 6271f663-7bc2-46fd-8676-105a09b4aa55@f40g2000pri.googlegroups.com
Xah <xahlee@gmail.com> writes:
Hi Xah,
> btw, what's the behavior of kill-line? Does it do screen line or EOL
> line?
It kills till EOL.
To make kill-line kill till the end of the screen line, you have to
enable visual-line-mode, which indeed changes line-wrapping, too. (It
does wrapping only on word boundaries and not inside words.)
Bye,
Tassilo
next prev parent reply other threads:[~2008-10-23 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1833.1224707092.25473.help-gnu-emacs@gnu.org>
2008-10-22 21:12 ` line-move-visual? Xah
2008-10-23 2:58 ` line-move-visual? Giorgos Keramidas
2008-10-23 10:46 ` Tassilo Horn [this message]
2008-10-22 20:24 line-move-visual? 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.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=87ljwf1tdx.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=help-gnu-emacs@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.
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).