From: Christian Barthel <bch@online.de>
To: moasenwood@zoho.eu
Cc: ding@gnus.org
Subject: Re: disable "You have lines longer than 79 characters. Really post? (y or n) y"
Date: Fri, 17 May 2019 08:33:06 +0200 [thread overview]
Message-ID: <871s0x8ual.fsf@x230.onfire.org> (raw)
In-Reply-To: <86v9yaqb72.fsf@zoho.eu> (Emanuel Berg's message of "Fri, 17 May 2019 00:36:01 +0200")
Emanuel Berg <moasenwood@zoho.eu> writes:
> Christian Barthel wrote:
>
> Well, hello there bch :) So it worked out at
> last! Great job :)
Sort of.. I just CC:'ed ding@gnus.org and it looks like
the post finally pops up here. (I added your mail in
the To: header because I wasn't sure if that would work
or will be rejected). I guess that I won't be able to
post to other groups where authentication is a required
thing.
> 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.
Yes, that's true.
>> 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?
Something like: https://bit.ly/2VOza3S
(Short-URL to emacs.stackexchange.com,
Title: How to edit crontab directly within emacs when I
already have emacs open?,
Estimated Size: 200k)
The drawback of this is that you have to go through
another service like bit.ly (or create your own) - but
nevertheless, there will be one redirect on the URL
consumer side.
In the case of stack*-.com pages, you can also strip
off the title because the number encodes the article
already. This would work, too:
https://emacs.stackexchange.com/questions/10077/
Depending on the configuration, website, content
management system etc. other such combinations are
possible.
[..]
> 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? :)
Nice setup, indeed.
--
Christian Barthel <bch@online.de>
next prev parent reply other threads:[~2019-05-17 6:33 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
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 [this message]
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=871s0x8ual.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).