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


Lennart Borgman <lennart.borgman@gmail.com> wrote:

> >> >> 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.
> >
> > The reasoning seems to be that the client is asking for html, and that's
> > what you're going to deliver to them... the fact that Mason is used to
> > generate the html is an internal detail there's no point in bothering
> > them with.
>
> Hm, I see. It is maybe a pretty good reason on that side. But do
> clients really care about the URL "file extension"?

Well, I do.  If the URL ends in ".asp", I think "oh, no...".





  reply	other threads:[~2009-12-12  2:16 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
2009-12-11 21:57             ` Joe Brenner
2009-12-11 22:06               ` Lennart Borgman
2009-12-12  2:16                 ` Joe Brenner [this message]
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=200912120216.nBC2GT1V070435@kzsu.stanford.edu \
    --to=doom@kzsu.stanford.edu \
    --cc=help-gnu-emacs@gnu.org \
    --cc=lennart.borgman@gmail.com \
    /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).