unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lucien Pullen <drurowin@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: [ELPA] Update package: psgml
Date: Wed, 19 Apr 2017 01:39:00 -0600	[thread overview]
Message-ID: <m0a87ckfsb.fsf@gmail.com> (raw)
In-Reply-To: <jwva87fxaey.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Mon, 17 Apr 2017 12:34:18 -0400")

Also sprach Stefan Monnier on 2017-04-17:
> Could you give some further details about the context where you bumped
> into the problem?

I'm doing a lot of DSSSL at the moment, and I wanted the SGML editor
commands to work in DSSSL mode.  With sgml-set-face turned on for
editing SGML structure, doing something like sgml-insert-element
fontifies for SGML up to point instead of fontifying for lisp because
PSGML fontifies as it parses the buffer to figure out the current
element.

> Hmm.. I like the goal, but I don't like lists of major-modes.
>
> Any reason why you couldn't set sgml-set-face to nil buffer-locally instead?

I actually wanted it to be mode-local, which emacs doesn't really do,
hence the list of major modes.  When in an SGML mode for editing markup,
I want the SGML to be fontified; when in some other mode for editing
notation data, I want that major mode's font locking to take place.

I can set sgml-set-face in a hook for sgml-mode, but then I have to
unset it if I want to edit in the other mode.  I figured a single list
of modes where SGML should be fontified would be easier to keep track of
than a slue of mode hooks.

I looked into indirect buffers, but this seems more intuitive.



  reply	other threads:[~2017-04-19  7:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16 22:38 [ELPA] Update package: psgml Lucien Pullen
2017-04-17 16:34 ` Stefan Monnier
2017-04-19  7:39   ` Lucien Pullen [this message]
2017-04-19 12:35     ` Stefan Monnier
2017-04-21  8:06       ` [ELPA] Update package: psgml (discard patch) Lucien Pullen
2017-04-21 14:00         ` Stefan Monnier
2017-04-26 10:50           ` Lucien Pullen
2017-04-26 12:34             ` 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=m0a87ckfsb.fsf@gmail.com \
    --to=drurowin@gmail.com \
    --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).