unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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 12:34:22 +0200	[thread overview]
Message-ID: <20170929103422.GF15026@tuxteam.de> (raw)
In-Reply-To: <86mv5dzu6z.fsf@zoho.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Sep 29, 2017 at 12:16:04PM +0200, Emanuel Berg wrote:
> tomás wrote:
> 
> > 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.
> 
> Yes, I understand :) Why do people think
> I don't understand all the time? Third time
> this thread!
> 
> Now yes, at this point it would be decipher but
> if you started using that language it would be
> reading and writing like any code.

After some period of training. Perhaps. But then... perhaps
not. This is one point where we might differ. I have the hunch
that there are some fundamental differences between people which
somehow shine through to what kind of language and culture they
gravitate to. Oversimplified, there are the Java types and the
Lisp types, or the Python types and the Perl types (note that
those two last languages are pretty similar, which at first
sight makes this rift the more paradoxical, but the language
cultures are utterly different), or the Eclipse types, the vi
types and the Emacs types.

If my hunch is correct, then there's no "right" language and
religion wars over that are just a waste of time. Get along and
be nice to each other and ponies and flowers and all that. And
keep in mind that saying "one must not write programs in C" [1],
to some, sounds like "you don't exist", which is a terrible
insult.

> Or well, not exactly like "any" code, because
> having code like that isn't healthy. It is
> un-ergonomic for the brain as well as the body.

See? That's where we disagree on. Easy to learn isn't always the
same as easy to use, And then (my hunch, at least), for whom.

Cheers

[1] "C", dear reader, should be read as a placeholder, of course.
   What did you think?
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlnOIa4ACgkQBcgs9XrR2kbGkwCfUiti9ijYCaf2hd5yB2WCT6NA
TycAnApj7GnOkCzhTS2uRlA6CtAwYOCf
=X0RC
-----END PGP SIGNATURE-----



  reply	other threads:[~2017-09-29 10:34 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
2017-09-29 10:16                     ` Emanuel Berg
2017-09-29 10:34                       ` tomas [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170929103422.GF15026@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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).