From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: Heime <heimeborgia@protonmail.com>
Cc: <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Make new buffer from menu
Date: Sun, 4 Dec 2022 12:55:23 +0100 [thread overview]
Message-ID: <25484.35499.308881.550044@tux.local> (raw)
In-Reply-To: Msg <5h9uQSeZVWQNo6OeB1lac6mQnYqWfJf2IWjomv-R470AYZXCp1XTXDqml7feE3C8NqCG-kmA46BveaNQlAuNnyLRednceriPZ1PymtdU3wc=@protonmail.com> of 2022-12-03 18:43:40 +0000 from heimeborgia@protonmail.com
Heime,
On Saturday, 2022-12-03 18:43:40 +0000, you wrote:
> ...
> The problem with Unsolicited Advice is that it is customarily useless.
Most probably this is as well an "Unsolicited Advice" according to your
above definition. But anyway:
> ...
> Using Emacs is like working on ice. It is extremely dangerous.
According to my _personal_ experience it's not more dangerous than driv-
ing a car. Your milage may vary. But in any case you are not at all
required to use an editor you classify as dangerous. There are plenty
of others around. I personally would never drive a Porsche, because I
simply do not want to drive that fast, thus making the Porsches's horse-
powers a total waste ...
And to stretch this example just a bit more: you do not learn driving a
car by perpetually asking questions, you learn it by supervised doing.
Here the supervision is necessary due to the real danger of driving on
public roads. But making blunders using Emacs is not dangerous at all,
provided you don't try something out using valuable data. Use a backup
copy, a test file or the "*scratch*" buffer to try your ideas. But in
any case remember what the acronym "RTFM" means before you send occa-
sionally very imprecise questions, assumptions or allegations to hun-
dreds of mailboxes. Get yourself acquainted with Emacs' documentation
(it isn't that bad after a while, or at least I've seen plenty of worse
product manuals).
Sincerely,
Rainer
next prev parent reply other threads:[~2022-12-04 11:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 3:58 Make new buffer from menu Heime
2022-12-03 17:20 ` [External] : " Drew Adams
2022-12-03 18:43 ` Heime
2022-12-03 19:15 ` tomas
2022-12-03 20:27 ` Heime
2022-12-04 6:20 ` tomas
2022-12-04 6:48 ` Eli Zaretskii
2022-12-04 7:20 ` Heime
2022-12-04 14:20 ` Jean Louis
2022-12-04 17:12 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-04 12:13 ` Jean Louis
2022-12-04 11:55 ` Dr Rainer Woitok [this message]
2022-12-04 12:32 ` Heime
2022-12-04 12:39 ` Jean Louis
2022-12-04 12:36 ` Jean Louis
2022-12-04 12:03 ` Jean Louis
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=25484.35499.308881.550044@tux.local \
--to=rainer.woitok@gmail.com \
--cc=heimeborgia@protonmail.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).