unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Major and minor modes
Date: Wed, 14 Jun 2017 13:39:55 +0200	[thread overview]
Message-ID: <87vany4x2s.fsf@debian.uxu> (raw)
In-Reply-To: 20170614095854.GA10795@tuxteam.de

<tomas@tuxteam.de> writes:

> Moreover, in this case, if you want to understand
> some random page you got from the Web (assuming you
> want to stay with your beloved Emacs), mixed-mode
> will come in handy. I know I appreciate it,
> for sure.

As for me, in the world of computers and in other
worlds as well, putting up with stuff that isn't to my
liking by tweaking tools only delay the inevitable
blow-up and failure.

If you don't like the way the dig is going, getting
the best shovels will not keep frustration at bay
for long.

> There are tons of those -- everything "domain
> specific language" goes a bit in that direction.

... - how exactly do you define that?

I always thought of Elisp, SQL, LaTeX, the dialects of
BASIC, etc. to be domain specific.

And I didn't mix up major modes every doing that!

-- 
underground experts united
http://user.it.uu.se/~embe8573




  parent reply	other threads:[~2017-06-14 11:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 23:58 Major and minor modes M.R.P.
2017-06-14  0:43 ` Jean-Christophe Helary
2017-06-14  1:49   ` Drew Adams
2017-06-14  3:49     ` Jean-Christophe Helary
2017-06-14  3:59       ` Emanuel Berg
2017-06-15  4:58         ` Marcin Borkowski
2017-06-14 14:23       ` Eli Zaretskii
2017-06-14 21:58         ` Jean-Christophe Helary
2017-06-14 23:10           ` Jean-Christophe Helary
2017-06-15 13:33             ` Emanuel Berg
2017-06-15 15:05           ` Eli Zaretskii
2017-06-15 15:16             ` Drew Adams
2017-06-16  2:09               ` Jean-Christophe Helary
2017-06-16  3:07                 ` Drew Adams
2017-06-16  4:44                   ` Emanuel Berg
2017-06-16  5:13                     ` Jean-Christophe Helary
2017-06-16  5:26                       ` Emanuel Berg
2017-06-16  6:59                   ` Eli Zaretskii
2017-06-16  8:02                     ` Jean-Christophe Helary
2017-06-16  4:34                 ` Emanuel Berg
2017-06-14  4:05     ` Emanuel Berg
2017-06-17 14:08       ` Narendra Joshi
2017-06-19  4:43         ` Krishnakant
2017-06-14  6:21     ` Krishnakant
2017-06-14  7:37     ` Phillip Lord
2017-06-14  1:54 ` Emanuel Berg
2017-06-14  7:40   ` Héctor Lahoz
2017-06-14  8:19     ` Emanuel Berg
2017-06-14  8:51       ` tomas
2017-06-14  9:25         ` Emanuel Berg
2017-06-14  9:36           ` Emanuel Berg
2017-06-14  9:58           ` tomas
2017-06-14 10:43             ` Emanuel Berg
2017-06-14 11:39             ` Emanuel Berg [this message]
2017-06-14 11:48               ` Emanuel Berg
2017-06-14 12:19               ` tomas
2017-06-14 14:15 ` Barry Margolin

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=87vany4x2s.fsf@debian.uxu \
    --to=moasen@zoho.com \
    --cc=help-gnu-emacs@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.
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).