unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Summer Emacs <summeremacs@summerstar.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Corwin Brust <corwin@bru.st>, emacs-devel@gnu.org
Subject: Re: Emacs Newbie Info Pages
Date: Fri, 13 Sep 2024 14:09:14 +0200	[thread overview]
Message-ID: <5C9D76A1-2247-4661-A8C7-75DB40E958ED@summerstar.me> (raw)
In-Reply-To: <86jzffkbpm.fsf@gnu.org>



> On Sep 13, 2024, at 13:57, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Summer Emacs <summeremacs@summerstar.me>
>> Date: Fri, 13 Sep 2024 13:20:33 +0200
>> Cc: Corwin Brust <corwin@bru.st>,
>> emacs-devel@gnu.org
>> 

<SNIP>

>> 
>> What do you think?
> 
> I think you should write the document and post it, and we can then
> take it from there.  This would be a good progress, IMO.

I can but it’s already something like 3 pages. And it’s just a framework.

> 
>> Also, if anyone else wants to collaborate on the document, I’m absolutely willing to do that
>> and I’m even hoping for it. Please let me know how to go about sharing this with others who are interested in
>> doing this. Do we set up a private email list? Do we collaborate on a git somewhere? I’m not sure how it all
>> works and I’m willing to learn. But I do want to get this done sometime. =)
> 
> It's basically up to you, I think.  If you want to set up a repository
> (preferably not GitHub, but if you must, that could also do), that's
> okay as a starting point.  We can leave the decision of how to proceed
> to later.

Ok. I can set up a git on GitHub later this evening or tomorrow and can post the info here I guess. I’ve never used GitHub like that - I just use it to store info for me. I’ll ask on IRC about the specifics on how to proceed before I post the info so I don’t get anything wrong.

Summer Emacs.





  reply	other threads:[~2024-09-13 12:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 17:30 Emacs Newbie Info Pages Summer Emacs
2024-09-12 18:26 ` Philip Kaludercic
2024-09-12 18:45   ` Summer Emacs
2024-09-12 19:17     ` Philip Kaludercic
2024-09-13  6:40       ` Eli Zaretskii
2024-09-13  7:36         ` Philip Kaludercic
2024-09-13  7:39       ` Summer Emacs
2024-09-13 14:46         ` Juergen Fenn
2024-09-13 12:28       ` Thanos Apollo
2024-09-12 18:29 ` Corwin Brust
2024-09-12 19:00   ` Summer Emacs
2024-09-13  2:24   ` Suhail Singh
2024-09-17  3:47     ` Richard Stallman
2024-09-17 10:58       ` Summer Emacs
2024-09-17 13:31         ` Eli Zaretskii
2024-09-17 14:12           ` Summer Emacs
2024-09-17 14:48             ` Emanuel Berg
2024-09-17 16:45               ` Summer Emacs
2024-09-18  1:09                 ` Emanuel Berg
2024-09-17 15:44             ` Eli Zaretskii
2024-09-17 16:49               ` Summer Emacs
2024-09-17 17:53                 ` Eli Zaretskii
2024-09-19  3:51         ` Richard Stallman
2024-09-19  9:45           ` Summer Emacs
2024-09-13  6:38   ` Eli Zaretskii
2024-09-13  7:45     ` Summer Emacs
2024-09-13 10:46       ` Eli Zaretskii
2024-09-13 11:20         ` Summer Emacs
2024-09-13 11:57           ` Eli Zaretskii
2024-09-13 12:09             ` Summer Emacs [this message]
2024-09-13 13:31               ` Eli Zaretskii
2024-09-18  8:13       ` Emanuel Berg
2024-09-18 20:02         ` Juergen Fenn
2024-09-20  2:39           ` Emanuel Berg
2024-09-22 12:37   ` Peter Oliver
2024-09-22 14:31     ` Eli Zaretskii
2024-09-13  6:35 ` Eli Zaretskii

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=5C9D76A1-2247-4661-A8C7-75DB40E958ED@summerstar.me \
    --to=summeremacs@summerstar.me \
    --cc=corwin@bru.st \
    --cc=eliz@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).