Wookey writes:
but I think I need to know the equivalent to
au FileType mail setlocal formatoptions+=w
for emacs particularly, but also zile, jed and mcedit (all of
which get used from time to time). Anyone know?
Set `use-hard-newlines' for emacs, according to
https://debbugs.gnu.org/cg
Package: general
Severity: important
X-Debbugs-Cc: vsa...@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was
Le Thu, Feb 27, 2025 at 09:48:44AM -0700, Soren Stoutner a écrit :
>
> > Currently, the code of conduct for the mailing lists says:
> >
> > "Wrap your lines at 80 characters or less for ordinary discussion. Lines
> > longer than 80 characters are acceptable for computer-generated output
> > (e.g
On 2025-02-27 13:29 +, Colin Watson wrote:
> On Wed, Feb 26, 2025 at 11:21:42AM -0700, Soren Stoutner wrote:
> > The purpose of this email is to propose that the expectation that emails
> > should be wrapped at 80 characters when they are sent should be dropped.
I admire your gumption for maki
At 15:53 + 27 Feb 2025, Jonathan Dowland wrote:
If you happen to use edit_headers, you *might* want something like this
(no idea if mutt has adopted it yet, ensures no trailing space on empty
header lines):
https://github.com/neomutt/neomutt/pull/1164
That PR shows as being merged sever
On Thu, Feb 27, 2025 at 03:53:41PM +, Jonathan Dowland wrote:
On Thu Feb 27, 2025 at 1:29 PM GMT, Colin Watson wrote:
And this in ~/.muttrc:
set text_flowed
That seems to work pretty well. I reflowed the parts of your
message that I quoted here to match.
If you happen to use edit_hea
On Wed, Feb 26, 2025 at 11:21:42AM -0700, Soren Stoutner wrote:
> I started thinking about this a few weeks ago when I received an email from a
> Debian Developer complaining that replies from my email client (KMail) looked
> odd because they truncated quoted lines in a way that did not lay out
Package: wnpp
Severity: normal
X-Debbugs-Cc: ost...@packages.debian.org, debian-devel@lists.debian.org,
sjo...@debian.org, m...@debian.org
Control: affects -1 + src:ostree
I request assistance with maintaining the ostree package.
(Other Uploaders cc'd.)
Package description:
libostree provides
On Thu, Feb 27, 2025 at 09:48:44AM -0700, Soren Stoutner wrote:
> Given the above four points, I propose the line from the code of conduct
> quoted above be
> changed to read:
lol, 22h after proposing to change 20 year old habbits, you still agree with
your idea. i'm not impressed. also you seem
On Wednesday, February 26, 2025 11:21:42 AM MST Soren Stoutner wrote:
> The purpose of this email is to propose that the expectation that emails
> should be wrapped at 80 characters when they are sent should be dropped.
This email has sparked an interesting discussion, which is what I was hoping
On Thu Feb 27, 2025 at 1:29 PM GMT, Colin Watson wrote:
And this in ~/.muttrc:
set text_flowed
That seems to work pretty well. I reflowed the parts of your message
that I quoted here to match.
If you happen to use edit_headers, you *might* want something like this
(no idea if mutt has a
Hello,
On Thu, 27 Feb 2025, at 15:18, Aurélien COUDERC wrote:
> See below how your message ends up being wrapped in my mobile client.
>
> That's readable for some strange/low value of $readable.
>>Le 27 février 2025 12:14:18 GMT+01:00, Vincent Lefevre a
>
> At least, 80-column text remains read
See below how your message ends up being wrapped in my mobile client.
That's readable for some strange/low value of $readable.
Agreed with Jonathan that if we can have senders and receivers understand
fixed-but-flowing lines, then good for everyone.
But that's obviously not the case currently a
On 2025-02-27 13:29:59 + (+), Colin Watson wrote:
[...]
I mostly read email in mutt in
a tmux shared with my IRC client, so I normally prefer to keep that
window fully maximized for the benefit of IRC, but email tends to be a
bit hard to read if it actually takes up the full width there
On Thu Feb 27, 2025 at 11:50 AM GMT, Tino Didriksen wrote:
format=flowed would be neat, if it was widely implemented. It is not.
And, we shouldn't require specific software to use the mailing lists.
We could widen its implementation, at least with software we supply (and
things like the BTS or
On Thu, Feb 27, 2025 at 7:30 AM Colin Watson wrote:
>
> On Wed, Feb 26, 2025 at 11:21:42AM -0700, Soren Stoutner wrote:
> >The purpose of this email is to propose that the expectation that
> >emails should be wrapped at 80 characters when they are sent should be
> >dropped.
> [...]
> >I understand
On Thu Feb 27, 2025 at 12:46 PM GMT, Andrej Shadura wrote:
That’s not entirely true: 80-column text often doesn’t fit on mobile
phone screens, and because it’s pre-formatted, it cannot be reflowed
easily, so it ends up an unreadable mess of alternating long and short
lines (the short ones being
Package: wnpp
Severity: wishlist
Owner: Karsten Schöke
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package name: python-esc-logging
Version : 2.2.0
Upstream Contact: Seth Michael Larson
URL :
License : Ap
On Wed, Feb 26, 2025 at 11:21:42AM -0700, Soren Stoutner wrote:
The purpose of this email is to propose that the expectation that
emails should be wrapped at 80 characters when they are sent should be
dropped.
[...]
I understand that there are historical reasons for the 80 character
limit, but
On 2025-02-27 at 07:46, Andrej Shadura wrote:
> Hello,
>
> On Thu, 27 Feb 2025, at 12:14, Vincent Lefevre wrote:
>
>> At least, 80-column text remains readable even on small screens,
>> contrary to most PDFs, which are also preformatted and are often
>> used nowadays (including as email conten
Hello,
On Thu, 27 Feb 2025, at 12:14, Vincent Lefevre wrote:
> At least, 80-column text remains readable even on small screens,
> contrary to most PDFs, which are also preformatted and are often
> used nowadays (including as email contents), even when this is not
> justified.
That’s not entirely
On Thu, Feb 27, 2025 at 12:50:30PM +0100, Tino Didriksen wrote:
> Wholeheartedly agree. Forced line wrapping is archaic, and not just in
> emails. Any viewer or editor worth anything can display long lines in a way
> that flows and indents with surroundings.
>
> format=flowed would be neat, if it
On Wed, 26 Feb 2025 at 19:21, Soren Stoutner wrote:
> The purpose of this email is to propose that the expectation that emails
> should be wrapped at 80 characters when they are sent should be dropped.
>
Wholeheartedly agree. Forced line wrapping is archaic, and not just in
emails. Any viewer or
* Jonathan Dowland [2025-02-27 09:21]:
Can we strongly recommend format=flowed instead?
+1
I've been using format=flowed for quite a while now, and it works
fine in general. The BTS website lacks rendering support for it,
which is the one place where flowed formatting would be useful for
me
On 2025-02-27 19:01:04 +0800, Blair Noctis wrote:
> It's kinda funny how in this world in 2025, where and when all
> computers possess processing power several magnitudes higher than
> Apollo Guidance Computer, some still believe that text should be
> pre-formatted to a fixed length no matter what,
* Charles Plessy [250227 10:12]:
> Le Thu, Feb 27, 2025 at 03:02:08PM +0800, Sean Whitton a écrit :
> >
> > Packages that already install programs to /usr/games, where another
> > package installs a program of the same with different functionality
> > to a different directory on the d
On 2025-02-26 18:38:41 +, Jeremy Stanley wrote:
> Mutt's default configuration handles non-wrapped long lines fairly
> gracefully, wrapping them at the last identifiable space character
> before the terminal's margin, or at the last character if it's an
> unbroken "word" longer than the termina
It's kinda funny how in this world in 2025, where and when all computers
possess processing power several magnitudes higher than Apollo Guidance
Computer, some still believe that text should be pre-formatted to a fixed
length no matter what, because their devices and/or reading facilities are,
On Thu, Feb 27, 2025 at 06:11:52PM +0900, Charles Plessy wrote:
> > Packages that already install programs to /usr/games, where another
> > package installs a program of the same with different functionality
> > to a different directory on the default PATH, may continue to do so.
>
> H
Can we strongly recommend format=flowed instead?
--
Please do not CC me for listmail.
👱🏻 Jonathan Dowland
✎j...@debian.org
🔗 https://jmtd.net
Le Thu, Feb 27, 2025 at 03:02:08PM +0800, Sean Whitton a écrit :
>
> Packages that already install programs to /usr/games, where another
> package installs a program of the same with different functionality
> to a different directory on the default PATH, may continue to do so.
Hi Sean
Hello,
On Wed, 26 Feb 2025, at 19:21, Soren Stoutner wrote:
> The purpose of this email is to propose that the expectation that emails
> should be wrapped at 80 characters when they are sent should be dropped.
>
Yes, please. Long due.
--
Cheers,
Andrej
32 matches
Mail list logo
