From: Eli Zaretskii <eliz@gnu.org>
To: Moakt Temporary Email <3c633ed3bb1f@drmail.in>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal: A Get Started introduction to emacs [was: An anonymous IRC user's opinion]
Date: Thu, 09 Jan 2025 17:38:25 +0200 [thread overview]
Message-ID: <86r05c0zgu.fsf@gnu.org> (raw)
In-Reply-To: <mYxjXi1RONuhvy3CX3LMPeU2WxOczcXhKtCdP7y4@localhost.localdomain> (message from Moakt Temporary Email on Thu, 9 Jan 2025 13:59:23 +0000)
> Date: Thu, 9 Jan 2025 13:59:23 +0000
> From: Moakt Temporary Email <3c633ed3bb1f@drmail.in>
>
> Hi Eli,
>
> I did not get a follow up on the “Get Started” introduction to emacs.
>
> By the way, I want to thank you for taking the time to read it. It took me some effort and time to write it, so I appreciate that.
>
> What is supposed to happen, so it can be added to emacs ?
>
> Do you want me to complete it (filling the empty dots) ?
>
> I wanted to do that initially, but I thought that you know emacs better than me, to choose the correct words, and I though that you would be reviewing/correcting it anyway, that is why I preferred keeping them empty. But I made an effort not to leave a lot, they are too few, and can be quickly filled.
Did you see my suggestions in this message:
https://lists.gnu.org/archive/html/emacs-devel/2024-12/msg00532.html
Since we already have customization groups and commands to present
them and allow users to look for the group(s) they need and customize
the relevant aspects, I feel that improving our groups (which
currently look not very rational or even helpful). The next step
would be to support intersections of groups.
WDYT?
next prev parent reply other threads:[~2025-01-09 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 13:59 Proposal: A Get Started introduction to emacs [was: An anonymous IRC user's opinion] Moakt Temporary Email
2025-01-09 15:38 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-03 2:19 Moakt Temporary Email
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86r05c0zgu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=3c633ed3bb1f@drmail.in \
--cc=emacs-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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.