URL:
<http://gna.org/bugs/?9337>
Summary: Deal with remote paths in publishing styles when
resolving links
Project: Emacs Muse
Submitted by: mwolson
Submitted on: Friday 06/15/2007 at 09:13
Category: muse
Severity: 3 - Normal
Priority: 1 - Later
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
It would be best to deal with this by calling muse-file-remote-p on a path,
and then using a different algorithm if it matches. Also, if we're
publishing to a remote path, prefer remote paths when resolving links.
Prefer non-remote paths when publishing to a non-remote path. Perhaps bail
out with a warning if we have a mix of remote and non-remote.
[Original email follows.]
Hi, I have just recently setup muse for managing a small website,
everything I have done I have been
able to solve it. I'm using few days ago arch tree:
muse--main--1.0--patch-346.
Well I have setup my project to be published to my hosting using tramp
and ftp this way:
'("project1"
("~/work/project1/src/" :default "menu")
(:base "my-xhtml" :path "~/work/project1/html/")
(:base "my-xhtml" :path "/ftp:[EMAIL PROTECTED]:www"))
While this work exactly as I intendet, it have now a problem with the
internal links
[[someplace][Some Place]]
In the xhtml I get a link:
<a href="$HOME/work/muse/project1/html/someplace.html">Some Place</a>
As you can see it has the absolute path on my home computer.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?9337>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Muse-el-commits mailing list
[email protected]
https://mail.gna.org/listinfo/muse-el-commits
