From: Jude DaShiell <jdashiel@panix.com>
To: Emanuel Berg <embe8573@student.uu.se>, help-gnu-emacs@gnu.org
Subject: Re: Even more Gnus material: we made the paper!
Date: Tue, 1 Mar 2016 21:11:01 -0500 (EST) [thread overview]
Message-ID: <alpine.NEB.2.20.1603012110140.22800@panix1.panix.com> (raw)
In-Reply-To: <87ziuhogi2.fsf@debian.uxu>
If I can get my graphics in ascii art especially for bar charts and
histograms I'm a happy camper.
On Wed, 2 Mar 2016, Emanuel Berg wrote:
> Date: Tue, 1 Mar 2016 19:44:37
> From: Emanuel Berg <embe8573@student.uu.se>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Even more Gnus material: we made the paper!
>
> Jonathan Groll <lists@groll.co.za> writes:
>
>>> And of course, Emacs is just one of the wide
>>> variety of "terminal-" or "shell-based" tools with
>>> which users operate their computers and use the
>>> Internet without the need for a graphical
>>> interface. Emanuel goes on to say he considers
>>> himself "text-based" and has largely "bypassed the
>>> Web." Other similar accounts can be easily found
>>> online of users who prefer "the warm glow of
>>> a green screen full of text over the cold
>>> blockiness of a graphical interface."
>>
>> Like most of us, I do mostly have a text-based view
>> of life although, under X Emacs lets me view office
>> docs, JPEGS and PDFs and surfing with w3m under X is
>> hardly "text-only".
>
> I use X as well to watch documentaries (and
> "Survivor") and to see my gnuplots and the result of
> my LaTeX - and, sometimes it is useful to Google the
> name of a tool and see its picture before you go to
> the shop.
>
> These are just examples but they are good examples.
>
> The idea is not to never use graphics, but rather do
> that when there is reason to do so and when there is
> not, instead present a uniform text display *and*
> input interface.
>
> The "cold blockiness of a graphical interface" is
> a good way to put it. I also think there is the aspect
> of authenticity or at least the perception of what is
> real. When you look at a good looking webpage or
> something else graphical the first time, it looks
> great and you are impressed. But the nth time, no
> matter how good it looks, your eye is so trained it
> still doesn't look real. It looks artificial. And it
> is! And it gets worse because to an extent you know or
> can guess how: this is HTML, this is CSS, this is
> JavaScript, this is...
>
> It is too much. So I just want text - like this, if
> you don't mind switching to X:
>
> http://user.it.uu.se/~embe8573/pics/text-mail.png
>
>
--
next prev parent reply other threads:[~2016-03-02 2:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 1:07 Even more Gnus material: we made the paper! Emanuel Berg
2016-02-29 15:45 ` Albin Ludvig Otterhäll
2016-03-02 0:22 ` Emanuel Berg
2016-02-29 16:48 ` Nick Dokos
2016-03-02 0:31 ` Emanuel Berg
2016-03-02 5:07 ` Marcin Borkowski
2016-03-01 6:51 ` Jonathan Groll
2016-03-02 0:44 ` Emanuel Berg
2016-03-02 2:11 ` Jude DaShiell [this message]
2016-03-02 2:36 ` Emanuel Berg
2016-03-02 2:44 ` Emanuel Berg
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=alpine.NEB.2.20.1603012110140.22800@panix1.panix.com \
--to=jdashiel@panix.com \
--cc=embe8573@student.uu.se \
--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).