unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs help from terminal
Date: Thu, 16 Jun 2022 19:31:32 +0200	[thread overview]
Message-ID: <87r13oa51n.fsf@dataswamp.org> (raw)
In-Reply-To: YqtHWu0VAos0dCIt@protected.localdomain

Jean Louis wrote:

> That somehow gives me impression that in this case of shell
> job suspension, you start thinking from your habits and
> assume that every computer user does the same.

Trust me, people don't do that anymore. And for good reason
since there is no advantage in controlling processes manually
at that level, if there is any need for that functionality
they should be given a proper interface that is
specialized/adapted for the situation, and in time, even that
should be fully automated.

> And I have given you quite a real example [...]

Jean, as you know a Spitfire and a Messersmith are aeroplanes.
They fly without any problem and to the layman quite aptly so.
But you don't have to be a flying ace to understand that
against an F-16 or a MiG they don't stand a chance. So you
see, to keep them "quite real" one has to keep them
VERY unemployed!

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2022-06-16 17:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 22:43 Emacs help from terminal carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-14  4:51 ` tomas
2022-06-14 10:11   ` Emanuel Berg
2022-06-14 13:38   ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-14 13:56     ` Samuel Banya
2022-06-14 14:03       ` Emanuel Berg
2022-06-14 13:57     ` tomas
2022-06-14 14:05       ` Emanuel Berg
2022-06-14 14:00     ` Emanuel Berg
2022-06-14 14:13       ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-14 14:37         ` Michael Heerdegen
2022-06-14 21:52           ` Jean Louis
2022-06-14 22:47             ` Emanuel Berg
2022-06-15  5:29               ` Jean Louis
2022-06-15  8:52                 ` Emanuel Berg
2022-06-15 17:00                   ` Tomas Hlavaty
2022-06-15 17:16                     ` Emanuel Berg
2022-06-15 19:55                     ` Emanuel Berg
2022-06-15 23:40                       ` Tomas Hlavaty
2022-06-15 23:52                         ` Emanuel Berg
2022-06-16  5:52                           ` Tomas Hlavaty
2022-06-16  7:12                             ` Emanuel Berg
2022-06-15 10:22             ` Michael Heerdegen
2022-06-15 10:26               ` Emanuel Berg
2022-06-15 14:06                 ` Samuel Banya
2022-06-15 14:15                   ` Robert Pluim
2022-06-15 15:16                     ` Emanuel Berg
2022-06-15 15:52                     ` Samuel Banya
2022-06-15 15:59                       ` Emanuel Berg
2022-06-16  7:48                       ` Robert Pluim
2022-06-16 14:45                         ` Samuel Banya
2022-06-16  5:34                     ` Jean Louis
2022-06-16  7:09                       ` Emanuel Berg
2022-06-16 15:08                         ` Jean Louis
2022-06-16 17:31                           ` Emanuel Berg [this message]
2022-06-16 17:36                             ` Jean Louis
2022-06-17 18:36                               ` 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=87r13oa51n.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --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).