Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: use-hard-newlines bizarre  (was: plain text, Ipod, format=flowed always)
Date: Tue, 08 Jan 2013 13:17:31 +0100	[thread overview]
Message-ID: <87pq1fyilg.fsf_-_@gilgamesch.quim.ucm.es> (raw)
In-Reply-To: <m3zk0snpio.fsf@stories.gnus.org>

[-- Attachment #1: Type: text/plain, Size: 885 bytes --]

>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes: 
 
   > Lars Magne Ingebrigtsen <larsi@gnus.org> writes: 
   >> This is a single paragraph with a long line of text that 
   >> should be long enough here. 
 
   > Yup.  Content-Type: text/plain; format=flowed 
 
I have the following in my setting 
 
(add-hook 'message-setup-hook 'my-use-hard-newlines) (defun 
my-use-hard-newlines () 
  (interactive) (use-hard-newlines) (describe-variable 
  use-hard-newlines)) 


Now when I create a new message I am asked make newlines hard.
I say n, but hardlines *is* turned ON, as shown by the describe
variables.

When I bind use-hard-newlines to a key, then the minibuffer correctly
informs me whether hardlines are on or not, so calling the function
interactively is ok, putting it in a hook is not. 

Any idea of this bizarre behaviour?

Uwe Brauer 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4474 bytes --]

  parent reply	other threads:[~2013-01-08 12:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 10:05 plain text, Ipod, format=flowed always Uwe Brauer
2012-12-24 20:09 ` Lars Ingebrigtsen
2012-12-28 13:52   ` Uwe Brauer
2012-12-31 15:28     ` Lars Magne Ingebrigtsen
2012-12-31 15:31       ` Lars Magne Ingebrigtsen
2013-01-01 17:18         ` Uwe Brauer
2013-01-01 20:00           ` Lars Magne Ingebrigtsen
2013-01-01 21:45             ` Uwe Brauer
2013-01-01 22:22         ` Elias Oltmanns
2013-01-02  5:02           ` Lars Magne Ingebrigtsen
2013-01-02  5:05             ` Lars Magne Ingebrigtsen
2013-01-08 11:21               ` Uwe Brauer
2013-01-08 23:54                 ` Greg Troxel
2013-01-14 11:32                   ` Uwe Brauer
2013-01-14 14:23                   ` [SOLVED] (was: plain text, Ipod, format=flowed always) Uwe Brauer
2013-01-08 12:17               ` Uwe Brauer [this message]
2013-01-10 18:16             ` Make newlines between paragraphs hard???? " Uwe Brauer

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=87pq1fyilg.fsf_-_@gilgamesch.quim.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=ding@gnus.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 NNTP newsgroup(s).