From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Modify text appearance (put spaces after commas just for display)
Date: Thu, 28 Sep 2017 18:54:45 +0200 [thread overview]
Message-ID: <863776227e.fsf@zoho.com> (raw)
In-Reply-To: ec791ddc-12e2-c2be-de1e-0634d4bcfe6a@kendallshaw.com
Kendall Shaw wrote:
>>> I think the OP didn't want to change the
>>> text itself, but just its
>>> display/appearance. So it will look one way
>>> and be another? Why would you do that?
>>
>
> Behold source for a J interpreter:
>
> http://code.jsoftware.com/wiki/Essays/Incunabulum
>
> Sorry for straying from the topic.
OK, good point, but if one doesn't believe in
the technology to begin with, using technology
one believes in to adapt and cope - I've tried
this several times, and *always* failed with
lots of frustration to it. A long time ago, of
course...
It took tons of time, and the result was never
even close to what one could have expected from
the "real/better deal".
Worst part was that all the adapting work felt
completely hopeless because one knew every
single second it was just a totally wasted
effort. So even tho it was programming,
I couldn't enjoy it one bit!
But hey, if you feel like it could work for
you, then don't do it :)
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-09-28 16:54 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
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 [this message]
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=863776227e.fsf@zoho.com \
--to=moasen@zoho.com \
--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).