From: Tassilo Horn <tsdh@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: visual line mode
Date: Fri, 12 Oct 2012 15:30:57 +0200 [thread overview]
Message-ID: <87obk7izqm.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: 1350042360640-266949.post@n5.nabble.com
drain <aeuster@gmail.com> writes:
>> Is it possibly that you still have visual-line-mode in some hooks?
>> What you describe sounds like global-visual-line-mode first turns on
>> VLM in your draft buffer, and then your hook turns it off again (or
>> the other way round).
>
> Not that I am aware of. When you launch compose-mail with
> global-visual-line mode (merely to reproduce my conditions), does it
> work for you?
Ah, ok. When I do:
1. emacs -Q
2. M-x global-visual-line-mode
3. M-x compose-mail RET
I get an *unsent mail* buffer in message-mode. `visual-line-mode' is
indeed active, but message-mode also activates `auto-fill-mode' which
automatically inserts hard line breaks after 72 chars by default.
So basically, you could add
(add-hook 'message-mode-hook 'turn-off-auto-fill)
to have `visual-line-mode' work as expected in message-mode. But do you
really want to send such badly formatted mail?
Bye,
Tassilo
next prev parent reply other threads:[~2012-10-12 13:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 6:56 visual line mode drain
2012-10-12 8:23 ` Tassilo Horn
2012-10-12 8:24 ` Eli Zaretskii
2012-10-12 8:48 ` Tassilo Horn
2012-10-12 10:35 ` drain
2012-10-12 10:45 ` Peter Dyballa
2012-10-12 10:48 ` drain
2012-10-12 11:27 ` Peter Dyballa
2012-10-12 11:36 ` Tassilo Horn
2012-10-12 13:32 ` Eli Zaretskii
2012-11-28 15:06 ` Matt McClure
2012-11-28 17:43 ` Eli Zaretskii
2012-11-29 3:34 ` Matt McClure
2012-11-29 13:49 ` Stefan Monnier
2012-12-01 3:28 ` Matt McClure
2012-10-12 15:51 ` Peter Dyballa
2012-10-12 13:28 ` Eli Zaretskii
2012-10-12 15:46 ` Peter Dyballa
2012-10-12 16:29 ` Eli Zaretskii
2012-10-12 22:06 ` Peter Dyballa
2012-10-13 7:41 ` Eli Zaretskii
2012-10-13 21:54 ` Peter Dyballa
2012-10-14 1:56 ` Bob Proulx
2012-10-14 5:44 ` Eli Zaretskii
2012-10-16 18:38 ` drain
2012-10-12 15:55 ` Peter Dyballa
2012-10-12 16:30 ` Eli Zaretskii
2012-10-12 21:40 ` Peter Dyballa
2012-10-13 7:36 ` Eli Zaretskii
2012-10-13 15:26 ` Peter Dyballa
2012-10-13 15:39 ` Eli Zaretskii
2012-10-12 11:03 ` Eli Zaretskii
2012-10-12 11:31 ` Tassilo Horn
2012-10-12 11:46 ` drain
2012-10-12 13:30 ` Tassilo Horn [this message]
2012-10-12 14:32 ` drain
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=87obk7izqm.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.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).