From: Tomi Ollila <tomi.ollila@iki.fi>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: wash: make word-wrap bound message width
Date: Mon, 22 Aug 2016 17:36:20 +0300 [thread overview]
Message-ID: <m2oa4k7twb.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <878tvpfgcx.fsf@qmul.ac.uk>
On Mon, Aug 22 2016, Mark Walters <markwalters1009@gmail.com> wrote:
> On Sat, 20 Aug 2016, Tomi Ollila <tomi.ollila@iki.fi> wrote:
>> On Wed, Jul 06 2016, Mark Walters <markwalters1009@gmail.com> wrote:
>>
>>
>> The change looks good to me -- but I just don't understand why someone
>> would set notmuch-wash-wrap-lines-length to something else than nil
>> -- and if it is set to some number what the behaviour should be ?
>
> I like to run notmuch in a very wide window as that make search view
> work better. But I don't like to read very wide text in show
> view. Emails sent from notmuch are fine as they hard-wrapped at
> something like 80 characters (usually), but some clients seem to make
> each paragraph one line and leave the recipient to wrap the text.
>
> notmuch-word-wrap-long-lines just controls where to wrap this text. The
> problem with the current version is that it ignores the indentation due
> to being deep in a thread, so if I set it to 80, then deep messages
> (even ones hard wrapped to 80) get wrapped at say 60 characters.
>
> Mine wraps at indentation+80 (if you set nw.w.l.l to 80) which means no
> hard-wrapped message get further wrapped however deep in a thread it is.
Now I understand. Does 999d473299781cb2a38fba5d9e2452504799a7a2 make this
stale ?
Tomi
>
> Best wishes
>
> Mark
>
next prev parent reply other threads:[~2016-08-22 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 7:47 [PATCH] emacs: wash: make word-wrap bound message width Mark Walters
2016-08-20 20:08 ` Tomi Ollila
2016-08-22 6:49 ` Mark Walters
2016-08-22 14:36 ` Tomi Ollila [this message]
2016-08-24 6:58 ` Mark Walters
2016-08-24 13:52 ` Tomi Ollila
2016-08-24 17:29 ` Mark Walters
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2oa4k7twb.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).