From: Peter Polidoro <peter@polidoro.io>
To: guix-devel@gnu.org
Subject: Thank you for using Emacs
Date: Mon, 18 Sep 2023 09:10:37 -0400 [thread overview]
Message-ID: <87bkdzmvs5.fsf@polidoro.io> (raw)
In-Reply-To: <mailman.9987.1694965840.1172.guix-devel@gnu.org>
MSavoritias <email@msavoritias.me> writes:
> I go to the manual to learn package management,
> https://guix.gnu.org/en/manual/devel/en/guix.html#Package-Management
>
> Apparently i have to either use the terminal or something called
> emacs.
> If I follow the guide located here:
> https://emacs-guix.gitlab.io/website/manual/latest/emacs-guix.html#Installation
>
> It says to install emacs-guix. Okay. So apparently it is an
> Emacs thing,
> whatever that means. And when you start Emacs after installing
> the
> package, you are going to end up with Emacs in its plain form.
> Unfamiliar keybindings, no autocomplete, etc. Well thats no to
> Emacs
> then. The other thing is the terminal apparently. Horrible, but
> at least
> it works.
You make a very good point, being exposed to Emacs for the very
first time in this way would be a terrible experience and listing
alternative options would be very beneficial.
However, I would just like to say "Thank you!" to everyone here
for using Emacs in the manual.
For my entire career in hardware engineering, I have felt like an
outcast for using Emacs and being passionate about free software.
When everyone else on a team or in a company or organization uses
proprietary software only, it is very isolating and career
limiting to stay committed to the free software and hardware
movements.
So while you may not win any popularity contests by using Emacs in
the manual, just know that it is very much appreciated by some of
us.
next parent reply other threads:[~2023-09-18 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.9987.1694965840.1172.guix-devel@gnu.org>
2023-09-18 13:10 ` Peter Polidoro [this message]
2023-09-18 14:45 ` Thank you for using Emacs MSavoritias
2023-09-18 14:51 ` Peter Polidoro
2023-09-19 0:06 ` kiasoc5
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkdzmvs5.fsf@polidoro.io \
--to=peter@polidoro.io \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).