all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 31571@debbugs.gnu.org, vikas@hackr.io
Subject: bug#31571: Regarding Emacs Learning Resources
Date: Mon, 12 Aug 2019 17:55:47 +0300	[thread overview]
Message-ID: <834l2mtouk.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnu3X2ZAD7SBYP+ZNDtRWBPx7CrTAx9H7hfkkL=LoS-QA@mail.gmail.com> (message from Stefan Kangas on Mon, 12 Aug 2019 04:00:34 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Mon, 12 Aug 2019 04:00:34 +0200
> Cc: 31571@debbugs.gnu.org
> 
> The only thing which really stands out as being absolutely worthy of
> addition is emacsrocks.com.  The other links had a lot of redundant
> material (already mentioned in the guide), were paid resources, or
> simply didn't look very professional or high quality.
> 
> On the other hand emacsrocks.com is already mentioned on the front
> page of the official Emacs web site, so it might be redundant.
> 
> https://www.gnu.org/software/emacs/
> 
> All of this is completely subjective, of course.  But I suggest to add
> the emacsrocks.com web site and close this.

Not sure I understand: where do you suggest to add a reference to
emacsrocks, given that it's already mentioned on the Emacs Web site?





  reply	other threads:[~2019-08-12 14:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23 15:55 bug#31571: Regarding Emacs Learning Resources Vikas from Hackr.io
2018-05-24  2:56 ` Richard Stallman
2018-05-24  9:41   ` Robert Pluim
2018-05-25  2:58     ` Richard Stallman
2019-08-12  2:00 ` Stefan Kangas
2019-08-12 14:55   ` Eli Zaretskii [this message]
2019-08-13  7:09     ` Stefan Kangas
2019-08-13  7:18       ` Stefan Kangas
2019-08-13 14:22         ` Eli Zaretskii
2019-08-14  8:29           ` Stefan Kangas

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=834l2mtouk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31571@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    --cc=vikas@hackr.io \
    /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.