Hi!
On Sun, 2025-03-16 at 18:55:52 +0100, Guillem Jover wrote:
> On Sun, 2025-03-16 at 18:18:58 +0100, Guillem Jover wrote:
> > […]
> > such as:
> >
> > # On time+3, Carol wrote:
> > # >On time+2, Bob wrote:
> > # >>On time+1, Alice wrote:
> > # >>>Some long reply line that supposedly get
On 3/16/25 6:40 PM, Paul Tagliamonte wrote:
> However, this GR is not flawed because Soren is a "new DD". That has
> nothing to do with this and -- with so much respect and affection for
> all of you -- I think that attitude fucking sucks. Soren has every right
> to suggest this GR. I just disagree
Hi!
On Sun, 2025-03-16 at 18:18:58 +0100, Guillem Jover wrote:
> […]
> such as:
>
> # On time+3, Carol wrote:
> # >On time+2, Bob wrote:
> # >>On time+1, Alice wrote:
> # >>>Some long reply line that supposedly gets wrapper at 7x chars or
> # >>>so, continued.
> # >>Some long reply l
On Sun, Mar 16, 2025 at 04:17:11PM +0200, Carsten Schoenert wrote:
With every email you write more about this non topic to obviously most
of the longer time DDs you disqualifies yourself more in my eyes.
[snip]
Sorry this is replying to you, Carsten -- this isn't about your message
really --
Hi!
On Thu, 2025-02-27 at 13:29:59 +, Colin Watson wrote:
This thread did, however, cause me to work out how to configure my
mailer to send format=flowed, since it does look as though that's
somewhat nicer for receivers who aren't using the same kind of
dinosaur setup as I am, and support se
Am 15.03.25 um 16:47 schrieb Soren Stoutner:
On Saturday, March 15, 2025 7:41:02 AM Mountain Standard Time Antonio Terceiro
wrote:
Please don't. Mobilizing the entire project to discuss and vote on the
exact format for sending plain text email is ridiculous. That silent
majority is silent, beca
Re: Soren Stoutner
> I thought about doing that, but those who are against this change feel so
> strongly about
> their position I don’t think they would accept a change made that way as
> valid. In
> addition, such a change doesn’t just need to apply to the mailing lists, but
> also to other
]] Soren Stoutner
Because the primary interaction that most people have with
Debian is through email, changing the way that interaction works
is a big enough issue that I don’t see any other appropriate way
of making it outside of a GR.
Given we've never established this by way of a GR, the
On Friday, March 14, 2025 2:49:26 PM Mountain Standard Time Soren Stoutner
wrote:
> On Wednesday, March 12, 2025 5:38:40 PM Mountain Standard Time Mario
> Limonciello
> wrote:
> >
> >
> > >Mario Limonciello (hints of format=flowed support)
> >
> > Thanks for the summary. I am of the camp of
On Saturday, March 15, 2025 11:19:25 AM Mountain Standard Time Andrea Pappacoda
wrote:
> Hi Soren,
>
> On Sat Mar 15, 2025 at 3:47 PM CET, Soren Stoutner wrote:
> > On Saturday, March 15, 2025 7:41:02 AM Mountain Standard Time Antonio
> >
> > Terceiro wrote:
> >> Please don't. Mobilizing the ent
Am Samstag, dem 15.03.2025 um 07:47 -0700 schrieb Soren Stoutner:
> It’s important enough to me.
Not important enough to fix your formatting and encoding, it appears.
Regards
signature.asc
Description: This is a digitally signed message part
Hi Soren,
On Sat Mar 15, 2025 at 3:47 PM CET, Soren Stoutner wrote:
On Saturday, March 15, 2025 7:41:02 AM Mountain Standard Time Antonio
Terceiro wrote:
Please don't. Mobilizing the entire project to discuss and vote on
the exact format for sending plain text email is ridiculous. That
silent
On Saturday, March 15, 2025 2:53:28 AM Mountain Standard Time Jonathan Dowland
wrote:
> On Fri Mar 14, 2025 at 9:49 PM GMT, Soren Stoutner wrote:
> > I am planning on proposing a GR, but I want to take the time to make
> > sure I word it well. I expect to be able to do so in the next few
> > days
On Saturday, March 15, 2025 3:08:01 AM Mountain Standard Time Stephan
Verbücheln
wrote:
> Am Montag, dem 03.03.2025 um 14:42 -0700 schrieb Soren Stoutner:
> > Interesting. I guess that text could be interpreted as “Do not send
> > an HTML part, even if you also send a plain text part.”
>
> Are
On Fri, Mar 14, 2025 at 02:49:26PM -0700, Soren Stoutner wrote:
On Wednesday, March 12, 2025 5:38:40 PM Mountain Standard Time Mario Limonciello
wrote:
>Mario Limonciello (hints of format=flowed support)
Thanks for the summary. I am of the camp of f=f.
At least with the MUA I'm using m
Thank you for the summation Phil!
To clarify my position: At present I am against the proposal.
Regarding format=flowed: I would not want the CoC complicated with it at
this time; I'd rather first gather more data on the current state of
client support, which MUAs are in popular use for Debian
On Mon Mar 10, 2025 at 1:41 PM GMT, Jeremy Stanley wrote:
My groff/troff reply to your earlier suggestion of this was only
somewhat tongue-in-cheek. Markdown isn't a singular clearly-specified
syntax, but a family of them with several popular flavors in
widespread use (as Timo's parser option c
On Saturday, March 15, 2025 7:41:02 AM Mountain Standard Time Antonio Terceiro
wrote:
> On Fri, Mar 14, 2025 at 02:49:26PM -0700, Soren Stoutner wrote:
> >On Wednesday, March 12, 2025 5:38:40 PM Mountain Standard Time Mario
> >Limonciello>
> >wrote:
> >>
> >>
> >> >Mario Limonciello (hints o
On Fri Mar 14, 2025 at 9:49 PM GMT, Soren Stoutner wrote:
I am planning on proposing a GR, but I want to take the time to make
sure I word it well. I expect to be able to do so in the next few
days.
Short of a GR, you could determine who "owns" the CoC at the moment:
it's not clearly a Debia
Am Montag, dem 03.03.2025 um 14:42 -0700 schrieb Soren Stoutner:
> Interesting. I guess that text could be interpreted as “Do not send
> an HTML part, even if you also send a plain text part.”
Are you serious? That does not make any sense.
> Please don't send your messages in HTML; use plain tex
On Wednesday, March 12, 2025 5:38:40 PM Mountain Standard Time Mario
Limonciello
wrote:
>
>
>
> >Mario Limonciello (hints of format=flowed support)
>
>
> Thanks for the summary. I am of the camp of f=f.
>
> At least with the MUA I'm using most of the time (Thunderbird) this is
> the de
Mario Limonciello (hints of format=flowed support)
Thanks for the summary. I am of the camp of f=f.
At least with the MUA I'm using most of the time (Thunderbird) this is
the default, and no one has complained to me directly about it for any
email sent to the Kernel community or Debian
The Wanderer writes:
> To be fair, while I *am* against the proposal, I'm also not a Debian
> Developer - just an interested observer of, and occasional participant
> in, discussions on Debian mailing lists (including this one).
+1
and to clarify my view on format=flowed:
This should not be ma
Before I did anything else, attempting to view your email in aerc
resulted in:
No filter configured for this mimetype ('text/markdown')
What would you like to do?
O Open using the system handler :open
S Save to file :save
| Pipe to shell command :pi
On Mon, Mar 10, 2025 at 11:03:49AM +0100, Julien Plissonneau Duquène wrote:
[text/markdown instead of text/plain]
That's IMO something much more interesting than text/html that should
be implemented in MUAs (falling back to displaying it as text/plain
eventually) but for now it doesn't display
On 2025-03-10 09:32:59 +0900 (+0900), Charles Plessy wrote:
[...]
I am also exploring the use of `text/markdown` as the default
content type for my emails.
My groff/troff reply to your earlier suggestion of this was only
somewhat tongue-in-cheek. Markdown isn't a singular
clearly-specified sy
On 09/03/2025 21:13, Philip Hands wrote:
(... some "vote" counting)
Thanks for the counting effort, Philip.
Though if you must put people into sides/camps,
put me in both/either
A. camp "one sentence/comma per line"
B. camp "why can't we just make the software able enough,
that they can reformat
Am Sonntag, dem 09.03.2025 um 22:13 +0100 schrieb Philip Hands:
> Stephan Verbücheln (against? at least against mixed HTML)
- against mixed HTML
- against unwrapped lines without a defined method/encoding
- okay with format=flowed
Disclaimer: Not a Debian developer.
Regards
signature.asc
Desc
Hi Phil,
* Philip Hands [2025-03-09 22:13]:
Of the 13 F=F folk, several also lean against the proposal to some
extent.
Just for the record, you may count me amongst them, too.
I'm sympathetic to the soft line wrap cause, but one line paragraphs in
text/plain is not a good solution IMHO.
Ch
Hi Charles,
Le 2025-03-10 01:32, Charles Plessy a écrit :
[text/markdown instead of text/plain]
That's IMO something much more interesting than text/html that should be
implemented in MUAs (falling back to displaying it as text/plain
eventually) but for now it doesn't display at all in som
Le Sun, Mar 09, 2025 at 10:13:51PM +0100, Philip Hands a écrit :
>
> Having skimmed through the 106 mails I currently see in this thread,
> this is the way I'd summarise people's preferences (if anyone sees that
> I've mis-characterised their view, I promise it was not intentional, so
> please forg
On 2025-03-09 14:13, Philip Hands wrote:
Having skimmed through the 106 mails I currently see in this thread,
this is the way I'd summarise people's preferences (if anyone sees that
I've mis-characterised their view, I promise it was not intentional, so
please forgive me and correct my mistake)
On Sun, Mar 09, 2025 at 10:13:51PM +0100, Philip Hands wrote:
> Soren Stoutner writes:
> > On Saturday, March 8, 2025 4:23:56 PM MST Philip Hands wrote:
> >> Soren Stoutner writes:
> >> > At this point in the discussion I would like to progress toward a
> >> > decision.
> >> >
> >> > One way to
Quoting Philip Hands (2025-03-09 22:13:51)
> Soren Stoutner writes:
>
> > On Saturday, March 8, 2025 4:23:56 PM MST Philip Hands wrote:
> >> Soren Stoutner writes:
> >> > At this point in the discussion I would like to progress toward a
> >> > decision.
> >> >
> >> > One way to do so would be
On 2025-03-09 at 17:13, Philip Hands wrote:
> Soren Stoutner writes:
>
>> On Saturday, March 8, 2025 4:23:56 PM MST Philip Hands wrote:
>>> You seem to be under the impression that there's an emerging
>>> consensus in favour of your idea.
>>
>> Yes, I feel like there are a majority of Debian D
Soren Stoutner writes:
> On Saturday, March 8, 2025 4:23:56 PM MST Philip Hands wrote:
>> Soren Stoutner writes:
>> > At this point in the discussion I would like to progress toward a decision.
>> >
>> > One way to do so would be a GR. On one hand, using a GR to modify one line
>> > of the cod
On 2025-03-09 Soren Stoutner wrote:
> On Saturday, March 8, 2025 4:23:56 PM MST Philip Hands wrote:
[...]
> > You seem to be under the impression that there's an emerging consensus
> > in favour of your idea.
> Yes, I feel like there are a majority of Debian Developers who are in favor
> of maki
Hi,
Le 2025-03-09 00:23, Philip Hands a écrit :
From my reading of this thread, the only real consensus seems to be
that
format=flowed is a good idea (as a result of which I intend to persuade
my mail setup to generate that when I've got a moment).
I doubt that a GR is justified, especially
On Saturday, March 8, 2025 4:23:56 PM MST Philip Hands wrote:
> Soren Stoutner writes:
> > At this point in the discussion I would like to progress toward a decision.
> >
> > One way to do so would be a GR. On one hand, using a GR to modify one line
> > of the code of conduct for the mailing lis
Soren Stoutner writes:
> At this point in the discussion I would like to progress toward a decision.
>
> One way to do so would be a GR. On one hand, using a GR to modify one line
> of the code of conduct for the mailing list seems like a rather large hammer
> for a rather small problem. But
On Fri, Mar 07, 2025 at 04:40:04PM -0700, Soren Stoutner wrote:
> My question is, is there any other decision making process that would be
> preferable to a GR to decide this issue?
another outcome would be to leave things like they are. of course we could
have a GR to get to that result too.
-
Am 8. März 2025 00:14:10 MEZ schrieb Thorsten Glaser :
>Otto Kekäläinen wrote:
>
>> I think this a reasonable suggestion by Soren. […]
>
>Incidentally, the suggestion is good as illegible on a
I think I'm misunderstanding something here, because - assuming you attached
the screenshot as an examp
At this point in the discussion I would like to progress toward a decision.
One way to do so would be a GR. On one hand, using a GR to modify one line
of the code of conduct for the mailing list seems like a rather large hammer
for a rather small problem. But on the other hand, many people fee
Otto Kekäläinen wrote:
> I think this a reasonable suggestion by Soren. […]
Incidentally, the suggestion is good as illegible on a
usual-to-read-longer-text-sized webbrowser on the mailing
list archive (and it would be almost as illegible on the
usual slightly wider-sized work xterm due to its in
On 2025-03-07 10:08:23 + (+), Jonathan Dowland wrote:
On Thu Mar 6, 2025 at 7:08 AM GMT, Henrik Ahlgren wrote:
> It is essential to have a method for distinguishing between hard
> and soft newlines if you want to reflow text properly.
Agreed! And, as Jeremy Stanley points out in anothe
On Thu Mar 6, 2025 at 7:08 AM GMT, Henrik Ahlgren wrote:
It is essential to have a method for distinguishing between hard and
soft newlines if you want to reflow text properly.
Agreed! And, as Jeremy Stanley points out in another msg, this is not
*quite* what format=flowed promises.
--
Pl
Quoting gregor herrmann (2025-03-07 00:14:19)
> On Thu, 06 Mar 2025 14:53:07 +0100, Giuseppe Sacco wrote:
>
> >I think that even for emails, the line length should be kept at a reasonable
> >value in order to maximize the readability. Such value is usually lower than
> >80, as shown, for example,
On Thu, 06 Mar 2025 14:53:07 +0100, Giuseppe Sacco wrote:
I think that even for emails, the line length should be kept at a reasonable
value in order to maximize the readability. Such value is usually lower than
80, as shown, for example, in
https://baymard.com/blog/line-length-readability . I d
Hello James,
Il giorno mer, 05/03/2025 alle 21.32 -0800, James Lu ha scritto:
> Hi all,
> On 2025-02-26 10:21, 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
> > (KMai
On 2025-03-06 at 00:32, James Lu wrote:
> Hi all,
>
> On 2025-02-26 10:21, Soren Stoutner wrote:
>> However, from a technical perspective, having the *sending* program
>> decide where line breaks should be in an email doesn’t seem like
>> the correct approach to me because, 1) the sending progr
On Wed, Mar 05, 2025 at 09:32:05PM -0800, James Lu wrote:
If I were to write, say, a Thunderbird extension that forcibly unwraps
text I receive, regardless of whether format=flowed was specified,
what would be the implication?
This (as a mild but easy to get example of pre-formatted text):
Fo
Andrey Rakhmatullin writes:
> This (as a mild but easy to get example of pre-formatted text):
>
>> For sake of argument:- If this re-wrapping is purely client side and
>> happens after PGP verification, incoming mail could still show as
>> verified (but it may look slightly different)- I could to
Hi all,
On 2025-02-26 10:21, 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 pleasingly. Th
On Wed, Mar 5, 2025 at 4:06 PM Otto Kekäläinen wrote:
>
> Hi!
>
> > Given the above four points, I propose the line from the code of conduct
> > quoted above be changed to read:
> >
> > “There is no expectation that emails sent to the mailing lists are wrapped
> > by the sender at a particular c
Hi!
> Given the above four points, I propose the line from the code of conduct
> quoted above be changed to read:
>
> “There is no expectation that emails sent to the mailing lists are wrapped by
> the sender at a particular column, but those sending emails may wrap them if
> they choose.”
>
>
On 2025-03-05 16:17:20 + (+), Jonathan Dowland wrote:
On Tue Mar 4, 2025 at 7:52 PM GMT, Soren Stoutner wrote:
> This is an interesting question based on a presumption that I didn’t
> know was possible. In a plain text email, is it possible to
> indicate that certain lines are not wrap
On Tue Mar 4, 2025 at 7:52 PM GMT, Soren Stoutner wrote:
This is an interesting question based on a presumption that I didn’t
know was possible. In a plain text email, is it possible to indicate
that certain lines are not wrappable?
Yes. That's exactly what format=flowed does. Line ends in sp
On Tuesday, March 4, 2025 5:43:07 PM MST Jeremy Stanley wrote:
> On 2025-03-05 08:52:22 +0900 (+0900), Charles Plessy wrote:
> [...]
>
> > I am surprised nobody has mentionned support (or lack of support) of
> > text/markdown at this point...
>
> [...]
>
> Surely you mean troff/groff?
> .Pp
> .B
On 2025-03-05 08:52:22 +0900 (+0900), Charles Plessy wrote:
[...]
I am surprised nobody has mentionned support (or lack of support) of
text/markdown at this point...
[...]
Surely you mean troff/groff?
.Pp
.Bd It's \fIthe best\fP!
;)
--
Jeremy Stanley
signature.asc
Description: PGP signature
Le Tue, Mar 04, 2025 at 12:52:39PM -0700, Soren Stoutner a écrit :
>
> This is an interesting question based on a presumption that I didn’t know was
> possible. In a plain text email, is it possible to indicate that certain
> lines are not wrappable?
I am surprised nobody has mentionned support
On Tuesday, March 4, 2025 5:08:43 AM MST Jonathan Dowland wrote:
> On Mon Mar 3, 2025 at 9:42 PM GMT, Soren Stoutner wrote:
> > Hence, I propose that we change the expectation so that the sending
> > MUA is not expected to wrap text.
>
> In which case, how can the receiving MUA know which lines ar
On Tue Mar 4, 2025 at 8:39 AM GMT, Henrik Ahlgren wrote:
Additionally, some messages contain sections that should never be
soft-wrapped, such as diffs. I'm uncertain whether many MUAs offer a
smooth user interface to designate which paragraphs should be
hard-wrapped. At least Gnus (message.el)
On Mon Mar 3, 2025 at 10:42 PM GMT, Soren Stoutner wrote:
From my perspective, the correct result is for this discussion to
reach the consensus that there is no expectation that sending MUAs
wrap text
I don't think we've reached that consensus in this discussion.
--
Please do not CC me for li
On Mon Mar 3, 2025 at 9:42 PM GMT, Soren Stoutner wrote:
Hence, I propose that we change the expectation so that the sending
MUA is not expected to wrap text.
In which case, how can the receiving MUA know which lines are wrappable
and which are not? Related, how can the sending MUA signal whic
On Mon Mar 3, 2025 at 5:39 PM GMT, Soren Stoutner wrote:
On Friday, February 28, 2025 7:30:53 PM MST Mason Loring Bliss
wrote:
Looks pretty awful to me. Screenshot attached.
Yes, the screenshot you sent shows how ugly it is when my email client
wraps sending emails at 80 columns. It is for t
"Andrea Pappacoda" writes:
As you can see, the Content-Type header has no Format parameter.
Yeah, (decoded) lines end with ' ' (ASCII space), but with no
Format parameter set to Flowed, they have no special meaning.
I stand corrected; I mistakenly interpreted f=f there. It seems
expectat
Hi Henrik,
On Mon Mar 3, 2025 at 10:12 PM CET, Henrik Ahlgren wrote:
Soren Stoutner writes:
All of the subsequent emails I have sent as part of this
discussion have been wrapped at 80 characters inline with the
current mailing list code of conduct.
If I'm not mistaken, your emails (at leas
> However, I would appreciate it if this discussion were not hijacked
> to discuss HTML vs. plain text.
In case we define any new rules, it has to cover both.
> That is interesting. I have Kmail set to wrap at 80 columns.
> However, it wouldn’t surprise me if Kmail has some bug in this
> regard
On Monday, March 3, 2025 3:26:36 PM MST Russ Allbery wrote:
> Soren Stoutner writes:
> > I agree. Having the sending MUA wrap text creates problems, even with
> > efforts like format=flowed that try to hint to the receiving MUA how to
> > unwrap the text.
>
> I am getting nerd-sniped here and rea
On 03/03/2025 19:10, Soren Stoutner wrote:
> On Monday, March 3, 2025 11:38:29 AM MST Philipp Kern wrote:
>> Mine doesn't wrap properly either, especially on wide screens. Neither
>> Thunderbird nor Roundcube. 80 characters are perfectly readable,
>> long-lines are increasingly annoying to read.
>>
Soren Stoutner writes:
> I agree. Having the sending MUA wrap text creates problems, even with
> efforts like format=flowed that try to hint to the receiving MUA how to
> unwrap the text.
I am getting nerd-sniped here and really should continue ignoring this
thread, but just for the record:
* Y
Am Montag, dem 03.03.2025 um 13:38 -0700 schrieb Soren Stoutner:
> Also, as I mentioned elsewhere in this thread, this is not a
> discussion about the merits of HTML vs plain text. As long as emails
> to the mailing list contain a plain text part, I know of no problem
> caused by them also contain
On Monday, March 3, 2025 2:28:38 PM MST Stephan Verbücheln wrote:
> Am Montag, dem 03.03.2025 um 13:38 -0700 schrieb Soren Stoutner:
> > Also, as I mentioned elsewhere in this thread, this is not a
> > discussion about the merits of HTML vs plain text. As long as emails
> > to the mailing list con
Soren Stoutner writes:
All of the subsequent emails I have sent as part of this
discussion have been wrapped at 80 characters inline with the
current mailing list code of conduct.
If I'm not mistaken, your emails (at least this one I am replying
to) utilize Format=Flowed (in the text/pain
On Monday, March 3, 2025 12:48:24 PM MST Jeremy Stanley wrote:
> On 2025-03-03 10:35:32 -0700 (-0700), Soren Stoutner wrote:
> [...]
>
> > I am not an expert on format=flowed, so I can’t vouch for the
> > following myself, but I thought it was interesting that the
> > article above linked to the f
On Monday, March 3, 2025 1:19:50 PM MST Stephan Verbücheln wrote:
> Are you aware that you are sending HTML messages the whole time?
Yes, as I mentioned elsewhere in this thread, the current version of Kmail
defaults to
sending both plain text and HMTL parts for every email.
Also, as I mentione
Are you aware that you are sending HTML messages the whole time?
Are you aware that in those HTML parts, the source code is limited to
80 characters per line?
Have you ever noticed that this is also the case for base64-encoded
binary attachments?
Are you aware that even the text/plain section of
On 2025-03-03 10:35:32 -0700 (-0700), Soren Stoutner wrote:
[...]
I am not an expert on format=flowed, so I can’t vouch for the
following myself, but I thought it was interesting that the
article above linked to the following:
https://wiki.openstack.org/wiki/MailingListEtiquette#Thunderbird
W
On Monday, March 3, 2025 11:38:29 AM MST Philipp Kern wrote:
> On 2025-03-03 18:39, Soren Stoutner wrote:
> > On Friday, February 28, 2025 7:30:53 PM MST Mason Loring Bliss
> >
> > wrote:
> >> Looks pretty awful to me. Screenshot attached.
> >
> > Yes, the screenshot you sent shows how ugly it is
On 2025-03-03 18:39, Soren Stoutner wrote:
On Friday, February 28, 2025 7:30:53 PM MST Mason Loring Bliss
wrote:
Looks pretty awful to me. Screenshot attached.
Yes, the screenshot you sent shows how ugly it is when my email client
wraps sending emails at 80 columns. It is for this reason I th
On Friday, February 28, 2025 7:30:53 PM MST Mason Loring Bliss
wrote:
> Looks pretty awful to me. Screenshot attached.
Yes, the screenshot you sent shows how ugly it is when my email client
wraps sending emails at 80 columns. It is for this reason I think we
ought to get rid of that and simply
On Sunday, March 2, 2025 9:50:47 AM MST Andrea Pappacoda wrote:
> >> https://www.fastmail.com/blog/format-flowed/
>
> Rather than "the little standard that couldnʼt quite make it", I'd
> call this article "the standard that we (Fastmail) wanted to support,
> but couldn't make it". More than highli
On 3/2/25 12:27, Marc Haber wrote:
On Mon, Mar 03, 2025 at 01:39:11AM +0800, Blair Noctis wrote:
I installed mutt and tried to reply to that email,
and mutt showed me the Content-Transfer-Encoding: base64 source.
I'm not sure if that's what you saw.
If you saw the decoded text,
I copied it in
On Mon, Mar 03, 2025 at 01:39:11AM +0800, Blair Noctis wrote:
I installed mutt and tried to reply to that email,
and mutt showed me the Content-Transfer-Encoding: base64 source.
I'm not sure if that's what you saw.
If you saw the decoded text,
I copied it into vim and vim seems to wrap it just fi
On Sun, 2 Mar 2025 21:14:54 +0800, Blair Noctis
wrote:
>Open source webmails also exist.
"When you're 10 out of 10 but it's your CVSS score".
Greetings
Marc
--
Marc Haber | " Questions are the | Maila
On 03/03/2025 01:08, Andrea Pappacoda wrote:
Hi Blair,
On Sun Mar 2, 2025 at 2:00 PM CET, Blair Noctis wrote:
FWIW, I've enabled format=flowed after learning it in this thread, hopefully
also giving those who would rather wrap some freedom (as to let it reflow,
which effectively means to wrap,
On 02/03/2025 18:12, Marc Haber wrote:
(...)
I am positively surprised that so many people in Debian still use mutt
(it's by far the most efficient way to handle large amounts of e-mail
including mailing lists"), so we need to cater for the fact that
e-mails are written in an entirely different s
Hi Blair,
On Sun Mar 2, 2025 at 2:00 PM CET, Blair Noctis wrote:
FWIW, I've enabled format=flowed after learning it in this thread,
hopefully also giving those who would rather wrap some freedom (as to
let it reflow, which effectively means to wrap, or not).
Yeah, this email has been sent wit
Il giorno sab 1 mar 2025 alle 09:48:36 +01:00:00, Timo Röhling
ha scritto:
* Soren Stoutner [2025-02-28 10:53]:
Format=flowed is being entirely driven by the belief that “We
really want the sending MUA to wrap text, but it creates horrible
problems, so here is a cludge to work around it.”
Q
Wrapping at 72 is intentional to allow a few levels of quotations. That
is where the slightly different numbers come from. The hard limit is 80
because of the 80x24 terminal convention.
Regards
signature.asc
Description: This is a digitally signed message part
On 01/03/2025 16:48, Timo Röhling wrote:
* Soren Stoutner [2025-02-28 10:53]:
(...)
https://www.fastmail.com/blog/format-flowed/
Only a webmail provider can bitch about the complexity of text wrapping and
then proceed to recommend HTML, which is even more complex to render and even
more dif
On Sun, Mar 02, 2025 at 09:00:21PM +0800, Blair Noctis wrote:
FWIW, I've enabled format=flowed after learning it in this thread, hopefully
also giving those who would rather wrap some freedom (as to let it reflow,
which effectively means to wrap, or not).
It's a bitch to reply to in mutt/vim.
On 01/03/2025 01:30, tho...@goirand.fr wrote:
On Feb 27, 2025 12:02, Blair Noctis wrote:
actually struggle to read the hard-wrapped-at-80-then-wrapped-again text.
The standard for email is 74 chars, not 80...
It's a rant. The actual number didn't matter.
But then again, I thought it's 80,
Quoting Marc Haber (2025-03-02 11:12:18)
> On Sat, 1 Mar 2025 09:48:36 +0100, Timo Röhling
> wrote:
> >* Soren Stoutner [2025-02-28 10:53]:
> >>Format=flowed is being entirely driven by the belief that “We really
> >>want the sending MUA to wrap text, but it creates horrible problems, so
> >>he
On Sat, 1 Mar 2025 09:48:36 +0100, Timo Röhling
wrote:
>* Soren Stoutner [2025-02-28 10:53]:
>>Format=flowed is being entirely driven by the belief that “We really
>>want the sending MUA to wrap text, but it creates horrible problems, so
>>here is a cludge to work around it.”
>I believe the ide
Le 28 février 2025 18:34:45 GMT+01:00, Jonathan McDowell a
écrit :
>On Fri, Feb 28, 2025 at 06:30:00PM +0100, tho...@goirand.fr wrote:
>> On Feb 27, 2025 12:02, Blair Noctis wrote:
>> > actually struggle to read the hard-wrapped-at-80-then-wrapped-again text.
>> The standard for email is 74 c
Hi,
* Soren Stoutner [2025-02-28 10:53]:
Format=flowed is being entirely driven by the belief that “We really
want the sending MUA to wrap text, but it creates horrible problems, so
here is a cludge to work around it.”
I believe the idea is more like "We want the receiving MUA to do the
line
On Fri, Feb 28, 2025 at 06:30:00PM +0100, tho...@goirand.fr wrote:
> On Feb 27, 2025 12:02, Blair Noctis wrote:
> > actually struggle to read the hard-wrapped-at-80-then-wrapped-again text.
> The standard for email is 74 chars, not 80...
RFC2822 says 78 characters.
https://datatracker.ietf.org/d
On Friday, February 28, 2025 10:37:51 AM MST Andrea Pappacoda wrote:
> [off-list]
>
> On Fri Feb 28, 2025 at 5:39 PM CET, Soren Stoutner wrote:
> > I agree with that. I think the above statement includes that for people who
> > already know what format=flowed is (and have an MUA that can do so),
On Fri, Feb 28, 2025 at 09:39:56AM -0700, Soren Stoutner wrote:
The CoC is a good place to list things it is not OK to complain to other people
about if
there is a high likelihood they are going to do so unless it is explicit,
especially when it
represents a change in long-standing behavior.
1 - 100 of 139 matches
Mail list logo
