From: Taco Hoekwater <taco@elvenkind.com>
To: ntg-context@ntg.nl
Subject: Re: texshow does not read t-vim.xml
Date: Sat, 17 Mar 2007 15:24:28 +0100 [thread overview]
Message-ID: <45FBFA1C.8090800@elvenkind.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0703171347130.31150@gaston.pm>
Peter Münster wrote:
> Hello,
>
> it seems, that texshow does not read t-vim.xml. Is this normal? How can I
> change it?
Yes, that is normal. Did you notice how the version number for texshow
is way below one? This is one of the reasons why that is so. At first,
I had no time to implement all features. Then, I was no longer happy
with perl. Then, the XML format was not complete enough to cover all
of the nice extensions in texshow-web. Even later, we wanted to create
a local http server using ruby (and reuse the texshow-web code), but we
could not figure out how to make that work reliably. And right now, we
have all these problems, combined.
Taco
prev parent reply other threads:[~2007-03-17 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 12:50 Peter Münster
2007-03-17 14:24 ` Taco Hoekwater [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45FBFA1C.8090800@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).