From: Tim Waugh <twaugh@redhat.com>
To: "Éric Bischoff" <e.bischoff@noos.fr>
Cc: Peter Toft <pto@sslug.dk>, docbook-tools-discuss@sources.redhat.com
Subject: Re: Any luck with DocBook/SGML 3.1 with Red Hat 7.3?
Date: Wed, 03 Jul 2002 23:33:00 -0000 [thread overview]
Message-ID: <20020704073302.F25750@redhat.com> (raw)
Message-ID: <20020703233300.4cI-czlKiw3OKsSlYK8hj4YB_o1ug24_HOQl4iyYg48@z> (raw)
In-Reply-To: <200207040616.26922.e.bischoff@noos.fr>; from e.bischoff@noos.fr on Thu, Jul 04, 2002 at 06:16:26AM +0200
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On Thu, Jul 04, 2002 at 06:16:26AM +0200, Éric Bischoff wrote:
> > Take a look at the docbook-utils.dsl file from the docbook-utils
> > tarball. This is what you're after I think. There is a more
> > complicated one in the Red Hat Linux docbook-utils RPM, too.
>
> The problem with this file is:
> - that it is shared among all users
> - that you need root access to modify it
>
> But I think that someone can simply achieve what we are speaking about by
> copying this file locally in his/her home directory, changing the desired
> options, and specifying on the command line that this file has to be used
> with the -d option.
Indeed, that's what I meant.
> Of course, jw and others could try such a local
> $HOME/.docbook-utils.dsl file without the user having to say that it
> should be used.
That would be a good idea, yes.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-07-04 6:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Peter Toft
2002-06-30 13:21 ` Peter Toft
2002-12-20 19:23 ` Tim Waugh
2002-06-30 14:02 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-07-01 0:49 ` Éric Bischoff
2002-12-20 19:23 ` Eric S. Raymond
2002-07-03 0:19 ` Eric S. Raymond
2002-12-20 19:23 ` Tim Waugh
2002-07-01 1:13 ` Tim Waugh
2002-12-20 19:23 ` Ismael Olea
2002-07-03 4:07 ` Ismael Olea
2002-12-20 19:23 ` Tim Waugh
2002-07-03 4:59 ` Tim Waugh
2002-12-20 19:23 ` Peter Toft
2002-07-01 14:22 ` Peter Toft
2002-12-20 19:23 ` Norman Walsh
2002-07-02 3:55 ` Norman Walsh
2002-12-20 19:23 ` Peter Toft
2002-07-02 13:48 ` Peter Toft
2002-12-20 19:23 ` Hugo van der Kooij
2002-07-03 13:59 ` Hugo van der Kooij
2002-12-20 19:23 ` Peter Toft
2002-07-03 14:01 ` Peter Toft
2002-12-20 19:23 ` Tim Waugh
2002-07-02 15:17 ` Tim Waugh
2002-12-20 19:23 ` Peter Toft
2002-07-03 13:50 ` Peter Toft
2002-12-20 19:23 ` Hugo van der Kooij
2002-07-03 14:04 ` Hugo van der Kooij
2002-12-20 19:23 ` Tim Waugh
2002-07-03 14:52 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-07-03 21:16 ` Éric Bischoff
2002-12-20 19:23 ` Tim Waugh [this message]
2002-07-03 23:33 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-07-04 2:51 ` Éric Bischoff
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=20020704073302.F25750@redhat.com \
--to=twaugh@redhat.com \
--cc=docbook-tools-discuss@sources.redhat.com \
--cc=e.bischoff@noos.fr \
--cc=pto@sslug.dk \
/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).