Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: ding@gnus.org
Subject: Re: disable "You have lines longer than 79 characters.  Really post? (y or n) y"
Date: Fri, 17 May 2019 00:36:01 +0200	[thread overview]
Message-ID: <86v9yaqb72.fsf@zoho.eu> (raw)
In-Reply-To: <87bm02vqlh.fsf@x230.onfire.org>

Christian Barthel wrote:

Well, hello there bch :) So it worked out at
last! Great job :)

> 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.

Yeah, but strange as it sounds, not everyone
uses Gnus, and also, that doesn't work on the
web archives which people browse with ordinary
browsers, often not even using a traditional
computer but a smartphone or tablet of
some sort.

> 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.

Hm, I'm not following 100%... how does that
work/look?

>> 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?

You mean the `fill-column'? It is 47, so good
estimate. So, how did I come up with that?
Well, I use a projector and Emacs in a Linux VT
with the font settings [1] at

FONTFACE="TerminusBold"
FONTSIZE="8x16"
SCREEN_HEIGHT=26
SCREEN_WIDTH=72

Here is a screenshot how it looks [2]

On the projector image on the wall, it
corresponds to a line width of (let me get my
folding rule) ~126cm (or ~49.5 inches) which
I think is just right.

Any questions? :)


[1] https://dataswamp.org/~incal/conf/vt/console-setup
[2] https://dataswamp.org/~incal/figures/gnus/gnus-post.png

-- 
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal




  parent reply	other threads:[~2019-05-16 22:36 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
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 [this message]
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=86v9yaqb72.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --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).