unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: karl@freefriends.org, emacs-devel@gnu.org
Subject: Re: ifinfo vs ifnottex
Date: Fri, 19 May 2006 20:46:09 -0500 (CDT)	[thread overview]
Message-ID: <200605200146.k4K1k9kI020993@jane.dms.auburn.edu> (raw)
In-Reply-To: <ufyj61dj4.fsf@gnu.org> (message from Eli Zaretskii on Fri, 19 May 2006 14:04:31 +0300)

Eli Zaretskii wrote:

   What is relevant, IMO, is whether we want to support any formats
   other than Info and DVI in the documentation directories.  (Note
   that the Makefile's currently don't support anything beyond these
   two formats.)

The basic problem is solved now and I installed my changes.  But I do
not immediately understand the above quote.  The Makefiles
automatically build .info files from the .texi files and install them.
I do _not_ consider the changes I just made to be a prelude for the
Makefiles to automatically build and install .html files.  What I was
worrying about was a user running `makeinfo --html' himself, maybe a
sysadmin who wants to provide links to manuals from a webpage.  I do
not believe that any support from the Makefiles is necessary for that.

Sincerely,

Luc.

  reply	other threads:[~2006-05-20  1:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18  2:53 ifinfo vs ifnottex Luc Teirlinck
2006-05-18  3:39 ` Eli Zaretskii
2006-05-18  4:15   ` Luc Teirlinck
2006-05-18 18:56     ` Eli Zaretskii
2006-05-18 20:29       ` Karl Berry
2006-05-19  3:32         ` Luc Teirlinck
2006-05-19 11:04           ` Eli Zaretskii
2006-05-20  1:46             ` Luc Teirlinck [this message]
2006-05-20  2:40             ` Luc Teirlinck
2006-05-20  8:46               ` Eli Zaretskii
2006-05-20 17:55                 ` Karl Berry
2006-05-20 18:44                   ` Eli Zaretskii
2006-05-21 17:08                     ` Richard Stallman
2006-05-21 18:44                       ` Eli Zaretskii
2006-05-21 21:07                         ` Karl Berry
2006-05-22  3:21                           ` Eli Zaretskii
2006-05-22 22:10                             ` Karl Berry
2006-05-19 18:05           ` Karl Berry
2006-05-19  9:40         ` Eli Zaretskii
2006-05-19 17:43           ` Karl Berry
2006-05-19 18:10             ` Eli Zaretskii
2006-05-20  5:04           ` Richard Stallman
2006-05-21  0:32             ` Luc Teirlinck
2006-05-18  4:47   ` Luc Teirlinck
2006-05-18  4:51   ` Luc Teirlinck
2006-05-19  2:04 ` Richard Stallman
2006-05-19  2:38   ` Luc Teirlinck
  -- strict thread matches above, loose matches on Subject: below --
2006-05-19 11:39 Robert J. Chassell

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=200605200146.k4K1k9kI020993@jane.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=karl@freefriends.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).