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: Wed, 27 Sep 2017 14:00:26 +0200	[thread overview]
Message-ID: <20170927120026.GB24821@tuxteam.de> (raw)
In-Reply-To: <86shf9174r.fsf@zoho.com>

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

On Tue, Sep 26, 2017 at 11:29:08PM +0200, Emanuel Berg wrote:
> tomás wrote:
> 
> > Why wouldn't you?
> 
> Because it is confusing.

Sorry. Wrong question (the "you" is ambiguous -- it might
mean either "you, Emanuel" or the generic, impersonal "you".
I meant the latter.

[...]

My whole point can be reduced to two things:

 (1) what we perceive as "literal display" is already the result
    of a more or less complex mapping; its undeniable advantage
    is, of course, that it is very conventional and thus large
    swaths of that mapping are already well-understood and relatively
    stable. But it's no better or worse (and no "truer" or "falser")
    than any other display.

 (2) there are other needs, views and preferences than the ones
    we currently understand. They are as important as ours.

One of the things I really like Emacs for is that, while it carries
the "plain text" paradigm very far (making Emacs, among other things
eminently understandable and hackable [1]), it doesn't close the door
on (2) (for an example on this, see e.g. Widget).

Cheers

[1] The very Org mode is a living proof to that.
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlnLktoACgkQBcgs9XrR2kaJZACdHtvztGtmKXQIoFsXcZSJgeem
85IAnRgT6FARFheDX6gRES86vmsq5svP
=jlG5
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2017-09-27 12:00 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 [this message]
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
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=20170927120026.GB24821@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).