unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Joseph Brenner <doom@kzsu.stanford.edu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Multiple Major Modes
Date: Fri, 11 Dec 2009 18:08:29 +0100	[thread overview]
Message-ID: <e01d8a50912110908o50bc0985id495c8c6019b9bb5@mail.gmail.com> (raw)
In-Reply-To: <87ljhaav81.fsf@kzsu.stanford.edu>

On Fri, Dec 11, 2009 at 7:19 AM, Joseph Brenner <doom@kzsu.stanford.edu> wrote:
>
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> Thanks for the answer Joseph. I just added some support for Mason
>> files to mumamo. It is not perfect (surprise! and there is an
>> indentation bug currently - those are very resistent to treatment),
>
> [...]
>
>> When you are in a Mason file turn do
>>
>>   M-x mason-html-mumamo-mode
>
> I've tried this, and I'm seeing syntax coloring in the HTML sections, but
> none in the perl sections.  Is that about what you expected?


I always expect some unexpected problems ... ;-)

But, no, it should of course do syntax coloring etc in the perl
sections too. Maybe I have misunderstood something. Can you give me an
example, please?


>> to test it. (BTW, what file extensions do Mason files normally have?)
>
> The currently recommended Mason file extensions are *.mhtml for internal
> components, and *.html for external ones:
>
>  http://www.masonhq.com/?FAQ:ServerConfiguration#h-what_filename_extensions_should_i_use_for_mason_components_
>
> That means, of course that the file extension alone gives you no way to
> distinguish between a plain html file and a top-level Mason file.


Thanks. I am a bit surprised by the second convention.


> Also there are other, older conventions: I've seen *.mc and *.mas in use
> (*.mas was used in the O'Reilly book on Mason).




  reply	other threads:[~2009-12-11 17:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29  9:45 Multiple Major Modes Nordlöw
2009-10-29 13:40 ` Pascal J. Bourguignon
2009-10-29 20:04 ` Joost Kremers
2009-10-29 22:14   ` Lennart Borgman
     [not found]   ` <mailman.9707.1256854525.2239.help-gnu-emacs@gnu.org>
2009-10-29 23:03     ` Pascal J. Bourguignon
2009-10-29 23:49       ` Lennart Borgman
     [not found]       ` <mailman.9710.1256860199.2239.help-gnu-emacs@gnu.org>
2009-10-30  0:52         ` Pascal J. Bourguignon
2009-10-30  3:28     ` Joseph Brenner
2009-11-01 23:14       ` Lennart Borgman
     [not found]       ` <mailman.9873.1257117309.2239.help-gnu-emacs@gnu.org>
2009-12-11  6:19         ` Joseph Brenner
2009-12-11 17:08           ` Lennart Borgman [this message]
2009-12-11 21:57             ` Joe Brenner
2009-12-11 22:06               ` Lennart Borgman
2009-12-12  2:16                 ` Joe Brenner
2009-12-12  2:18                   ` Lennart Borgman
2009-12-12  2:37                     ` Joe Brenner
2009-11-01 21:24 ` Dave Love
2009-11-02 12:32   ` Lennart Borgman
2009-11-02 14:01   ` Richard Riley
2009-11-02 14:22     ` Lennart Borgman
2009-11-02 14:28       ` Richard Riley
2009-11-02 14:44         ` Richard Riley
2009-11-02 15:11     ` Richard Riley
  -- strict thread matches above, loose matches on Subject: below --
2008-06-10 21:26 Nordlöw
2008-06-10 21:47 ` Lennart Borgman (gmail)
2008-06-11  5:42 ` William Xu

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=e01d8a50912110908o50bc0985id495c8c6019b9bb5@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=doom@kzsu.stanford.edu \
    --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).