unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alan Mackenzie <acm@muc.de>
Subject: Re: emacs for everything?
Date: Fri, 19 Nov 2004 19:41:31 +0000	[thread overview]
Message-ID: <b9ilnc.td.ln@acm.acm> (raw)
In-Reply-To: 87hdnmmzp4.fld@barrow.com

Floyd L. Davidson <floyd@barrow.com> wrote on Thu, 18 Nov 2004 15:48:07 -0900:
> Alan Mackenzie <acm@muc.de> wrote:

>>> I would like to know how you use your fingers and brain to remember
>>> the _current_ time on a clock that you do not display?  (As just one
>>> very trivial example of how limited your described environment is in
>>> a real world.)

>>I don't - I just look up at the device hanging on the wall, or glance
>>at

> You missed the point, again Alan.  As I noted, that is a trivial
> example.  It demonstrates the point, but is not meant to flag a
> significant usage.  It shows that there are applications which present
> data that cannot be remembered simply because the data changes (or the
> data set is too large to be remembered, or too detailed, or whatever).

It doesn't show anything of the kind.  Applications which use a lot of
data belong in their own screen, and that is how I use them.

> For that application to be useful on a computer, as opposed having to
> hang it on the wall ....

Having the time displayed on a computer isn't useful to me.

> In addition to a clock on my computer screen, I also have two
> other programs displaying information that is dynamically
> updated.  Having them available via keyboard commands is
> certainly possible, but the point was that such a mechanism
> reduces productivity.

Is this other information useful?  What is it?  The FSF's current share
price, the proportion of your screen currently covered by windows, the
air temperature in Moscow, or what?

> Indeed, the entire point of my comments has been that what you are
> describing is *not* a very productive arrangement.

<sigh>  I thought we'd dealt with that point.  My setup is productive for
me, whilst your setup is, presumably, productive for you.

> Whether you are satisfied with a non-productive work environment is
> beyond the scope of my interest, or the topic of this newsgroup, though
> I will say that hopefully your attitude relates only to your personal
> work, because an employer should probably terminate you for cause under
> those circumstances.

LOL!  Is your employer aware that his employee is a clock-watcher?

>>the one strapped to my left wrist.  If, for any reason, I wanted to
>>know my computer's idea of the time, I'd type in "date" and press the
>>carriage return key.  And if I really, really, really badly wanted it
>>continuously displayed on my console, I'd get Emacs to display it on
>>the mode-line.  How to do this is described in the Emacs manual on the
>>page "Optional Mode Line", if you're interested.  I don't, though.

> You can trust that I'm probably far more familiar with displaying data
> on the modeline that you are.

I doubt that.

> However, the mode line is only so wide and so high, and can't display
> very much.  Something trivial like the date and time it can do quite
> well.  But it can't show me much about what is on this or that web page
> which I might be using to research something I'm writing...

Right.  Now we're coming to the way you use a computer.  This likely has
a lot to do with why you have such a complicated way of using it.

>>Questions:  Do you have the time displayed continuously on your screen?
>>If so, why?  Did you chose to have it there, or did your window manager
>>put it there by default, as it were.  What do you get out of it?

> I wrote the program that displays the time on my screen.

Do you get out much?

> I also have a very much customized modeline for my emacs, which shows
> the current date and time in a way that is distinctly different from
> the default.

Do you get out much?

> What I get out of it is the increased productivity of having a known to
> be accurate time standard (wall clocks here are not accurate), and
> (this is the important part, so listen up) I can observe the time
> without having to interrupt whatever I am typing.

Now you're missing the point.  How on earth does having the time
displayed increase your productivity?  Do you have to write the time into
your documents a lot, thus making it useful to be able to copy it
directly from your screen?  Or is it a kind of background comfort, a kind
of soothing certainty, a bit like some people play music through
headphones as they work?  How would your work (or even your play) suffer
if there wasn't a clock visible on the screen?  What difference would it
make to your productivity if you just used the clock on the wall, and it
was 5 seconds out?  Or even 5 minutes?  I'm genuinely interested.

I don't have a clock on my screen, and I don't need one.

> Floyd L. Davidson

-- 
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").

  reply	other threads:[~2004-11-19 19:41 UTC|newest]

Thread overview: 105+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15  1:29 emacs for everything? Mike
2004-11-15  2:30 ` Henrik S. Hansen
2004-11-15 14:52   ` Per Abrahamsen
2004-11-15 16:32     ` Henrik S. Hansen
2004-11-16 10:09   ` William Xuuu
2004-11-16 13:20     ` Floyd L. Davidson
2004-11-16 20:07       ` Alan Mackenzie
2004-11-17 13:22         ` Oliver Scholz
2004-11-17 15:30         ` Thien-Thi Nguyen
2004-11-17 18:45         ` Floyd L. Davidson
2004-11-17 20:11           ` Thien-Thi Nguyen
2004-11-17 22:07           ` Henrik S. Hansen
2004-11-18 18:51           ` Alan Mackenzie
2004-11-18 22:03             ` Stefan Monnier
2004-11-19  0:48             ` Floyd L. Davidson
2004-11-19 19:41               ` Alan Mackenzie [this message]
2004-11-19 19:00         ` Cristian Gutierrez
2004-11-19 20:29           ` Leonardo Boiko
2004-11-26  4:51       ` William Xuuu
2004-11-23 12:27     ` Alex Polite
2004-12-06  2:39       ` David Combs
2004-11-15  2:51 ` V. L. Simpson
2004-11-15  3:03 ` David Hansen
2004-11-15  3:17 ` Galen Boyer
2004-11-15  7:06 ` Kin Cho
2004-11-16  1:57   ` Joe Fineman
2004-11-15  7:37 ` Gian Uberto Lauri
2004-11-15 12:56 ` Pascal Bourguignon
2004-11-15 13:09 ` respower
2004-11-15 14:37 ` Thien-Thi Nguyen
2004-11-17 13:27   ` Oliver Scholz
2004-11-16 11:00 ` Kai Grossjohann
     [not found] ` <mailman.3054.1100603433.8225.help-gnu-emacs@gnu.org>
2004-11-16 15:41   ` Mathias Dahl
  -- strict thread matches above, loose matches on Subject: below --
2004-11-16  5:41 Joe Corneli
     [not found] ` <mailman.3197.1100662500.8225.help-gnu-emacs@gnu.org>
2004-11-16 11:58   ` Fabian Braennstroem
2004-11-17 19:05     ` Floyd L. Davidson
2004-11-20 17:19       ` Kai Grossjohann
2004-11-21  9:17         ` Janusz S. Bień
     [not found]         ` <mailman.363.1101029322.27204.help-gnu-emacs@gnu.org>
2004-12-05  1:23           ` Zajcev Evgeny
     [not found]       ` <mailman.236.1100971735.27204.help-gnu-emacs@gnu.org>
2004-11-20 18:18         ` Pascal Bourguignon
2004-11-20 21:40           ` Jay Belanger
2004-11-20 23:05             ` Alan Mackenzie
2004-11-21  9:29               ` Joe Corneli
2004-11-21 16:22             ` Pascal Bourguignon
2004-11-20 18:45         ` Floyd L. Davidson
2004-11-22 10:27           ` Kai Grossjohann
2004-11-22 13:50             ` John Sullivan
2004-11-23 19:57             ` Maciek Pasternacki
2004-11-25 13:31               ` Kai Grossjohann
2004-11-25 14:52                 ` Maciek Pasternacki
2004-11-26  9:03                   ` Kai Grossjohann
2004-11-27 17:12                     ` Maciek Pasternacki
2004-11-27 19:50                       ` Kai Grossjohann
2004-11-28  1:29                         ` Maciek Pasternacki
2004-11-28 11:47                           ` Kai Grossjohann
2004-11-27 23:16                       ` Daniel Pittman
     [not found]               ` <mailman.1437.1101390082.27204.help-gnu-emacs@gnu.org>
2004-11-25 15:19                 ` Mike
2004-11-25 15:45                   ` Maciek Pasternacki
     [not found]             ` <mailman.1058.1101240531.27204.help-gnu-emacs@gnu.org>
2004-11-24  4:13               ` Lee Sau Dan
2004-11-24 13:10                 ` Maciek Pasternacki
2004-11-24 14:25                   ` Leonardo Boiko
2004-11-24 20:33                     ` Maciek Pasternacki
2004-11-24 20:49                       ` Leonardo Boiko
     [not found]                       ` <mailman.1312.1101329987.27204.help-gnu-emacs@gnu.org>
2004-12-01 17:49                         ` Kevin Rodgers
     [not found]                     ` <mailman.1308.1101329036.27204.help-gnu-emacs@gnu.org>
2004-11-25  3:16                       ` Pascal Bourguignon
2004-11-25 13:16                         ` Maciek Pasternacki
     [not found]                         ` <mailman.1434.1101389211.27204.help-gnu-emacs@gnu.org>
2004-11-25 20:12                           ` Stefan Monnier
2004-11-25 21:03                             ` Maciek Pasternacki
     [not found]                             ` <mailman.1503.1101417224.27204.help-gnu-emacs@gnu.org>
2004-11-27 22:00                               ` Stefan Monnier
2004-11-28  1:31                                 ` Maciek Pasternacki
2004-11-25 17:06                       ` Mathias Dahl
2004-11-28 14:29                       ` Lee Sau Dan
2004-11-28 20:24                         ` Joe Corneli
2004-11-30 10:00                     ` ken
     [not found]           ` <mailman.591.1101120112.27204.help-gnu-emacs@gnu.org>
2004-11-24 23:58             ` Floyd L. Davidson
2004-11-27 20:07               ` Kai Grossjohann
2004-11-27 23:08                 ` Micha Feigin
2004-11-28  1:33                 ` Maciek Pasternacki
     [not found]                 ` <mailman.1945.1101634177.27204.help-gnu-emacs@gnu.org>
2004-11-28 12:24                   ` Floyd L. Davidson
2004-11-29 11:56                     ` Kai Grossjohann
     [not found]                     ` <mailman.2151.1101729999.27204.help-gnu-emacs@gnu.org>
2004-11-29 15:11                       ` Floyd L. Davidson
2004-12-01 16:34                         ` Kai Grossjohann
     [not found]                         ` <mailman.2811.1101919485.27204.help-gnu-emacs@gnu.org>
2004-12-03 19:55                           ` Floyd L. Davidson
     [not found]               ` <mailman.1836.1101586658.27204.help-gnu-emacs@gnu.org>
2004-11-27 22:00                 ` Floyd L. Davidson
2004-11-28 18:36                 ` David Hansen
2004-11-18 19:47     ` Alan Mackenzie
2004-11-17 20:50   ` Alan Mackenzie
2004-11-17 22:46     ` Joe Corneli
     [not found]     ` <mailman.3419.1100732160.8225.help-gnu-emacs@gnu.org>
2004-11-18 19:42       ` Alan Mackenzie
2004-11-18 22:41         ` Joe Corneli
2004-11-17  3:24 ` Joe Corneli
     [not found] <mailman.2999.1100584262.8225.help-gnu-emacs@gnu.org>
2004-12-06  2:44 ` David Combs
2004-12-06  4:11   ` Pascal Bourguignon
2004-12-27  1:59     ` David Combs
2004-12-30  7:04       ` Ravi Uday
2004-12-30  7:30         ` Neon Absentius
     [not found]         ` <mailman.9951.1104392583.27204.help-gnu-emacs@gnu.org>
2004-12-30  9:32           ` Ravi Uday
2004-12-30  9:53             ` Christian Plate
2004-12-30  9:59             ` Neon Absentius
2004-12-30 10:17             ` Peter Dyballa
2004-12-30 12:25             ` kurtz
2004-12-30 15:11             ` Floyd L. Davidson
2004-12-30 15:27               ` David Kastrup
2004-12-30 16:33                 ` Floyd L. Davidson
2004-12-30 16:39                   ` David Kastrup

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=b9ilnc.td.ln@acm.acm \
    --to=acm@muc.de \
    /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).