From: Christian Barthel <bch@online.de>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: ding@gnus.org
Subject: Re: disable "You have lines longer than 79 characters. Really post? (y or n) y"
Date: Thu, 16 May 2019 08:52:10 +0200 [thread overview]
Message-ID: <87bm02vqlh.fsf@x230.onfire.org> (raw)
In-Reply-To: <86bm07ywua.fsf@zoho.eu> (Emanuel Berg's message of "Mon, 13 May 2019 03:19:57 +0200")
Emanuel Berg <moasenwood@zoho.eu> writes:
> I get this question every second or third mail
> I send. URLs are long today.
true.
> An example from a gmane.emacs.help thread post
> I just posted is
>
Personally, I prefer breaking the URL at the "natural"
line length and use the Gnus "unsplit URL" (W u) to
bring them back in full length and click on it.
The URL would become something like that:
https://emacs.stackexchange.com/questions/10077/
how-to-edit-crontab-directly-within-emacs-when-
i-already-have-emacs-open
An alternative approach that I do sometimes is to use
my own url shortener service and post that instead. I
always write the Content-Type, Size and origin below
the URL.
> Col 120! So it it by a safe margin (indeed, 41
> chars, or >150%) one can say that the 79 char
> warning limit is exaggerated...
Out of curiosity, how did you come up with your line
length of being somewhere below 50 chars?
[..]
--
Christian Barthel <bch@online.de>
next prev parent reply other threads:[~2019-05-16 6:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 1:19 Emanuel Berg
2019-05-13 3:12 ` Eric Abrahamsen
2019-05-13 5:31 ` Emanuel Berg
2019-05-13 5:45 ` Emanuel Berg
2019-05-16 6:52 ` Christian Barthel [this message]
2019-05-16 16:48 ` Eric Abrahamsen
2019-05-16 18:25 ` Andreas Schwab
2019-05-16 18:33 ` Eric Abrahamsen
2019-05-16 22:36 ` Emanuel Berg
2019-05-16 23:05 ` (where) is ding@gnus.org archived? (was: Re: disable "You have lines longer than 79 characters. Really post? (y or n) y") Emanuel Berg
2019-05-17 1:25 ` disable "You have lines longer than 79 characters. Really post? (y or n) y" Eric Abrahamsen
2019-05-17 2:02 ` Emanuel Berg
2019-05-17 6:33 ` Christian Barthel
2019-05-18 17:10 ` Emanuel Berg
2019-05-22 17:08 ` Christian Barthel
2019-05-27 20:53 ` Emanuel Berg
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=87bm02vqlh.fsf@x230.onfire.org \
--to=bch@online.de \
--cc=ding@gnus.org \
--cc=moasenwood@zoho.eu \
/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).