Gnus development mailing list
 help / color / mirror / Atom feed
From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: ding@gnus.org
Subject: Re: text/plain with 80 char wrap vs the flowed mime-type (whatever it is)
Date: Fri, 05 Feb 2016 12:13:04 -0500	[thread overview]
Message-ID: <87y4azrsgv.fsf@yale.edu> (raw)
In-Reply-To: <m2mvrhnq28.fsf@gmail.com>

Hi, Mark.

Mark Simpson writes:

> Jorge A. Alfaro-Murillo) writes: 
> 
>> (add-hook 'message-mode-hook 'use-hard-newlines) 
> 
> I have not had luck with that, specifically with cited text. Do 
> you have luck with it and cited text?

Most of the time I actually do not want to have hard newlines for 
cited text. For example citing you above I still want it with 
format=flowed, generally mail viewers do a good job presenting it 
in the right way for any line length, at least emacs and my 
android phone do. If you really want a hard newline you can use 
C-m or C-o to insert it. The only issue I have is when copying 
code. Generally I yank the code, mark the region and use 
multiple-cursors mc/edit-ends-of-lines to insert the hard 
newlines. I should write some code for a special yank that 
substitutes newlines for hard-newlines.

> I use supercite but I don't know if that matters.

I do not use supercite, so I don't know either.

-- 
Jorge.




  parent reply	other threads:[~2016-02-05 17:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 21:59 Wes Hardaker
2016-01-28  1:52 ` Jorge A. Alfaro-Murillo
2016-02-02 18:22   ` Wes Hardaker
2016-02-04  2:54   ` Mark Simpson
2016-02-04  5:18     ` Teemu Likonen
2016-02-04 14:30       ` Teemu Likonen
2016-02-05  0:21         ` Mark Simpson
2016-02-05 17:13     ` Jorge A. Alfaro-Murillo [this message]
2016-02-04 16:17   ` Nikolaus Rath
2016-02-04 22:41 Magnus Henoch
2016-02-05  0:14 ` Nikolaus Rath
2016-02-05  0:22 ` Mark Simpson

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=87y4azrsgv.fsf@yale.edu \
    --to=jorge.alfaro-murillo@yale.edu \
    --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).