I don't know how you've structured things, but I think, from a user
perspective, that it would be fine to just have sub-sections on the html
page, something like:

Tramp Filename conventions

FSF GNU emacs:  

        blah blah /[EMAIL PROTECTED]:/path/to/file  blah blah

XEmacs

        blah blah /[EMAIL PROTECTED]/path/to/file blah blah


I also actually think that would be fine in the info file as well,
because whatever is currently there to switch which section is rendered,
didn't work.  I'm using XEmacs on a RedHat 7.3 machine, and I upgraded
my tramp package using the package facility, and there is _still_ no
mention of different XEmacs conventions...

Thanks,

H

On Wed, 2003-03-05 at 09:16, Michael Albinus wrote:
> Hunter Kelly <[EMAIL PROTECTED]> writes:
> 
> > However, I was reading the documentation off of the web, which doesn't
> > mention that the syntax is different for XEmacs under the filename
> > conventions heading.  It makes a mention that there is a different
> > example for XEmacs using multihop, but then doesn't include it.
> > 
> > And a quick check of the info file shows that the differences aren't
> > mentioned there, either...
> 
> Oops, indeed. I'll add a note to the top page for which flavor of
> Emacs this has been created, and how to get the other incarnation.
> 
> Kai: should we offer _both_ HTML versions on the project homepage?
> 
> > H
> 
> Best regards, Michael.
> 
> 



_______________________________________________
Tramp-devel mailing list
[EMAIL PROTECTED]
http://mail.nongnu.org/mailman/listinfo/tramp-devel

Reply via email to