unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: binarydigitz01 <binarydigitz01@proton.me>
Cc: emacs-devel@gnu.org
Subject: Re: TODO: Major modes should have a menu entry
Date: Fri, 1 Jul 2022 09:10:44 +0300	[thread overview]
Message-ID: <Yr6P5O2fB/zYt6OD@protected.localdomain> (raw)
In-Reply-To: <23kuBCiAL_iJkF9eImYTZYAvr0OrQGfgawBYLn3lcm2rwm0CqlFJPcGs_n9PAJccHlKcs8DL52VP9UmUNjyZJUFXpD3PgIyLja7JUN8iarg=@proton.me>

* binarydigitz01 <binarydigitz01@proton.me> [2022-06-29 20:07]:
> Thanks for the reply! I was taking a look, and it seems that
> there are a lot of major modes in emacs, do we have to put them all
> in a menu, or are there any specific ones? etc/TODO doesn't mention
> any details.

Hello,

I propose to you to ask for feedback from people if that is really
necessary and needed and wanted.

Do you find that need from observing how other editors do it?

What makes you personally need that?

Personally, I do not have a need for the menu.

The way I choose major modes is just by letting Emacs decide it for
me when opening a file.

Issue that I have encountered is that when opening a string instead of
a file or string stored in the database, then it becomes difficult for
Emacs to recognize which major mode should be such. In that case I may
be editing HTML with CSS, but text-mode is chosen automatically.

The way how I solved this issue is that for those pieces of text in
the database which have their markup like Markdown, Org, Asciidoctor,
etc. I have a major mode tied to the markup type. So if I open string
of Markdown, then markup type tells to Emacs which major mode and
minor modes to turn on.

There are some strings where I do not have direct relation of string
to markup, so in that case I plan in future to have separate table of
attributes where specific table, specific column, including specific
ID number has specific major mode. 

Recommended reading: (info "(emacs) Major Modes")

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  parent reply	other threads:[~2022-07-01  6:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  6:48 TODO: Major modes should have a menu entry binarydigitz01 via Emacs development discussions.
2022-06-29 10:25 ` binarydigitz01 via Emacs development discussions.
2022-06-29 13:20   ` Jean Louis
     [not found]     ` <23kuBCiAL_iJkF9eImYTZYAvr0OrQGfgawBYLn3lcm2rwm0CqlFJPcGs_n9PAJccHlKcs8DL52VP9UmUNjyZJUFXpD3PgIyLja7JUN8iarg=@proton.me>
2022-07-01  6:10       ` Jean Louis [this message]
2022-07-01 12:19         ` Stefan Monnier

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=Yr6P5O2fB/zYt6OD@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=binarydigitz01@proton.me \
    --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).