unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 39556@debbugs.gnu.org
Subject: bug#39556: 27.0.60; Org Mode menu item comes before Elisp item?
Date: Mon, 10 Feb 2020 15:20:29 -0800 (PST)	[thread overview]
Message-ID: <ee59b89a-1ca4-4a51-8c2e-e2e7dae183f9@default> (raw)

`C-h i' shows:

Emacs
* Emacs: (emacs).               The extensible self-documenting text editor.
* Emacs FAQ: (efaq).            Frequently Asked Questions about Emacs.
* Emacs W32 FAQ: (efaq-w32).    FAQs about Emacs on MS Windows.
* Org Mode: (org).              Outline-based notes management and organizer.
* Elisp: (elisp).               The Emacs Lisp Reference Manual.
* Emacs Lisp Intro: (eintr).    A simple introduction to Emacs Lisp 
                                  programming.

Really?  Was this intended?

How is Org mode different from, say, Gnus?  Or Tramp?  Or Dired?  Or
Ediff?  Or EWW?  Or any number of other features?  Why was it elevated
so?  Before Elisp?

Here's one vote to move it back down with the other specific modes.  At
least please move it out of the first group, which is for Emacs as a
whole and Elisp.



In GNU Emacs 27.0.60 (build 1, x86_64-w64-mingw32)
 of 2019-12-28
Repository revision: 21c3020fcec0a32122d2680a391864a75393031b
Windowing system distributor `Microsoft Corp.', version 10.0.18362
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install -C 'CFLAGS=-O2 -static -g3''





             reply	other threads:[~2020-02-10 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 23:20 Drew Adams [this message]
2020-02-11 16:27 ` bug#39556: 27.0.60; Org Mode menu item comes before Elisp item? Stephen Berman
2020-02-12 23:31   ` Bastien
2020-02-12 23:41     ` Drew Adams
2020-02-13  0:00     ` Stephen Berman
2020-02-13  8:42       ` Bastien

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=ee59b89a-1ca4-4a51-8c2e-e2e7dae183f9@default \
    --to=drew.adams@oracle.com \
    --cc=39556@debbugs.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).