From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Modify text appearance (put spaces after commas just for display)
Date: Fri, 29 Sep 2017 09:19:01 +0200 [thread overview]
Message-ID: <20170929071901.GA15026@tuxteam.de> (raw)
In-Reply-To: <86vak2ypir.fsf@zoho.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Sep 29, 2017 at 08:42:20AM +0200, Emanuel Berg wrote:
[...]
> > I'm certain they could read code
> > like that (I can't).
>
> Sure you can, and write it as well, but for how
> long before your eyes and head would start to
> ache and your whole system communicate "don't
> do it" the minute you sit down by the keyboard?
I guess I should be more precise, then. I was using "read"
in some "literate" sense, as I would read a text. Wha I'd
do with this kind of code would be more "decipher". I is
a much more deliberate (and painful) process.
My point is that those folks most probably "read" this code
in this more literate way, the way I might, e.g. "read" C
code by R. W. Stevens or Knuth's "METAFONT The Program".
Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlnN8+UACgkQBcgs9XrR2kZlmwCfZR32ruQcOw3ZJgQRVcs7niwI
4eAAn0tMiLJjoz6sPpkehQNLd4fH7NO0
=t7VG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-09-29 7:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 9:12 Modify text appearance (put spaces after commas just for display) Alberto Luaces
2017-09-26 9:28 ` Emanuel Berg
2017-09-26 9:31 ` Alberto Luaces
2017-09-26 9:32 ` tomas
2017-09-26 10:14 ` Emanuel Berg
2017-09-26 10:30 ` tomas
2017-09-26 11:08 ` Alberto Luaces
2017-09-26 21:29 ` Emanuel Berg
2017-09-27 6:23 ` Marcin Borkowski
2017-09-27 8:20 ` Emanuel Berg
2017-09-27 12:07 ` tomas
2017-09-27 21:40 ` Emanuel Berg
2017-09-28 6:55 ` tomas
[not found] ` <mailman.229.1506975352.27995.help-gnu-emacs@gnu.org>
2017-10-03 1:57 ` James K. Lowden
2017-10-03 2:49 ` Emanuel Berg
2017-09-27 12:00 ` tomas
2017-09-27 21:30 ` Emanuel Berg
2017-09-28 8:40 ` Kendall Shaw
2017-09-28 11:27 ` Alberto Luaces
2017-09-28 12:09 ` tomas
2017-09-28 16:42 ` Emanuel Berg
2017-09-28 17:18 ` tomas
2017-09-29 6:42 ` Emanuel Berg
2017-09-29 7:19 ` tomas [this message]
2017-09-29 10:16 ` Emanuel Berg
2017-09-29 10:34 ` tomas
2017-09-29 11:40 ` Emanuel Berg
2017-09-29 2:02 ` Kendall Shaw
2017-09-29 6:45 ` Emanuel Berg
2017-09-28 16:54 ` Emanuel Berg
2017-09-26 10:00 ` Yuri Khan
2017-09-26 11:05 ` Alberto Luaces
2017-09-26 13:11 ` Marcin Borkowski
2017-09-26 16:36 ` Alberto Luaces
2017-09-26 13:26 ` Nick Helm
2017-09-26 16:34 ` Alberto Luaces
2017-09-26 14:15 ` Sivaram Neelakantan
2017-09-26 16:39 ` Alberto Luaces
2017-09-29 12:12 ` Eli Zaretskii
2017-09-29 13:59 ` Alberto Luaces
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=20170929071901.GA15026@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.