Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: What's the best server and how do you setup gnus in emacs?
Date: Sun, 03 Aug 2014 00:47:12 +0200	[thread overview]
Message-ID: <87silewlu7.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.6485.1407013150.1147.info-gnus-english@gnu.org>

asjo@koldfront.dk (Adam Sjøgren) writes:

>>> The lack of a left margin does not seem to bother
>>> you, though?
>>
>> No, because that is a straight line so it is a clear
>> enough delimiter in itself.
>
> You were comparing to books - they have margins at
> both sides of the text - so that made me wonder...

Yes, I got you thinking.

Books have two margins, true. But the "outer" margin
(the one at the edge of the page, not the one where
both pages meet) is the one the widest. Either, it
actually is wider, or it gets wider by the binding.

I don't know why, but I consider a editor buffer to be
the right hand side of a book, if I had to pick one of
the two.

But the book comparison isn't the best come to think of
it. The reason is that books have their right (text)
margin straight as well. That makes the whitespace
margin less important as it is clear where the line is
anyway. If I could get that in Gnus, I could have it 70
as well (or perhaps 65, but then I have to solve that
other problem as well).

>>> Maybe using a proportional font might be of use to
>>> you, when width is constrained?
>>
>> What, you mean when "l"s are thin and "M" wide and
>> so on? Oh, no.
>
> Yes, like, you know, in books.

But not in programming or computer work. That would
bring chaos to everything. Just think of all
indentation. I could give you a thousand examples, but
let's say - this:

(let ((files (with-temp-buffer
               (call-process-shell-command
                "ls ~/.emacs.d/emacs-init/**/*.elc ~/.emacs-no-bc"
                nil ; no INFILE
                t)  ; BUFFER (t = current buffer, i.e. the temp one)
               (buffer-substring (point-min)
                                 (point-max)) )))
  (dolist (f (split-string files)) (load-file f)) )

How would that look? And how would it be carried out? I
don't know how auto-indentation would handle a
proportional font, only manually - which will always be
necessary if you want it a certain way, and with
functions (e.g., [1]), shortcuts, and finger habits
that's actually rather relaxing and pleasant work...

Also, isn't Usenet monospaced? If so, don't you want it
to look the same way in your client as other people
will see it - the actual text, at least?

> The conclusion is different strokes for different
> folks, I guess - just don't be surprised when people
> think your articles look strange, not using the
> recommended default line width.

Well, actually that would surprise me as the difference
shouldn't be that radical. It is just a line width
that's - let's see - 78.6% the default. Is that really
that radical? But I am used to see everything "my way"
as your posts are at 55 as well, when I read them. If
they weren't, and I read my own posts, perhaps I would
react to the difference (?).

By the way, I counted the chars in a newspaper which
had 4 columns a page - 32 chars! - for a randomly
picked line. I don't know what fill-column that would
be - 40? In "Black Belt", as I mentioned: 3 columns, 42
chars.

Is this easier to read? (It is a bit unscientific as
you had "training" reading it. Also, as said, I think
the professional newspapers guys and girls write in a
certain way to fit the form, probably short sentences
and paragraphs where the heavy information first, and
no complicated sentence structure (or parenthesis that
makes you loose track...) - uhm, what did I just say?
Oh, yeah, is this easier to read?

(setq fill-column 40)

By the way, I counted the chars in a
newspaper which had 4 columns a page -
32 chars! - for a randomly picked line.
I don't know what fill-column that would
be - 40? In "Black Belt", as I
mentioned: 3 columns, 42 chars.

[1] http://user.it.uu.se/~embe8573/conf/emacs-init/align.el

-- 
underground experts united
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

      parent reply	other threads:[~2014-08-02 22:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02  0:39 thezsak
2014-08-02  2:48 ` Emanuel Berg
2014-08-02  7:46   ` Glyn Millington
     [not found]   ` <mailman.6449.1406966691.1147.info-gnus-english@gnu.org>
2014-08-02 17:24     ` Emanuel Berg
2014-08-02 17:35       ` Adam Sjøgren
2014-08-02 17:46       ` Glyn Millington
     [not found]       ` <mailman.6473.1407000937.1147.info-gnus-english@gnu.org>
2014-08-02 17:53         ` Emanuel Berg
2014-08-02 19:21           ` Adam Sjøgren
     [not found]           ` <mailman.6482.1407007322.1147.info-gnus-english@gnu.org>
2014-08-02 20:04             ` Emanuel Berg
2014-08-02 20:34               ` Adam Sjøgren
     [not found]               ` <mailman.6483.1407011685.1147.info-gnus-english@gnu.org>
2014-08-02 20:49                 ` Emanuel Berg
2014-08-02 20:58                   ` Adam Sjøgren
     [not found]                   ` <mailman.6485.1407013150.1147.info-gnus-english@gnu.org>
2014-08-02 22:47                     ` Emanuel Berg [this message]

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=87silewlu7.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=info-gnus-english@gnu.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).