all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: Ulrich Mueller <ulm@gentoo.org>,
	Christian Egli <christian.egli@sbs.ch>,
	Stefan Monnier <monnier@IRO.UMontreal.CA>,
	emacs-devel@gnu.org
Subject: Re: BBDB v3 approaching release
Date: Thu, 30 May 2013 17:04:52 +0900	[thread overview]
Message-ID: <878v2wdhaz.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <20902.64600.858912.770771@gargle.gargle.HOWL>

Roland Winkler writes:

 > In a texmf installation, these files would go into a directory like
 > /usr/local/share/texmf/bbdb 
 > I do not know where other TeX installations expect to find such files.
 > 
 > Can the ELPA format handle such files, too?  How?

TeX is happy to pick up such files from the current directory.  Why
would it be a problem?  If that doesn't work or the BBDB includes are
shadowed, TEXINPUTS=.:$TEXINPUTS should do the trick.  man kpathsea
for more information about telling TeX where to find stuff.

But mostly people are going to do such formatting in a proper source
tree.  Not your problem.  The GPL (maybe, but certainly FLOSS
courtesy) requires that you provide a "script" (ie, Makefile) to
rebuild if people want to modify in-place, but for the info files that
can be as simple as

bbdb.info: bbdb.texi
	makeinfo bbdb.texi

bbdb.html: bbdb.texi
	makeinfo --html bbdb.texi

bbdb.pdf: bbdb.texi <style files ...>
	makeinfo --pdf bbdb.texi

At least, I should think so.  If you normally use @setfilename to put
the info etc someplace other than the current directory, use the -o
option to put it in the current directory.







  parent reply	other threads:[~2013-05-30  8:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27  8:18 BBDB v3 approaching release Roland Winkler
2013-05-27  8:49 ` Leo Liu
2013-05-27 15:13   ` Stefan Monnier
2013-05-27 16:13     ` Roland Winkler
2013-05-27 16:57       ` Stefan Monnier
2013-05-27 19:28         ` Roland Winkler
2013-05-27 19:35           ` Dmitry Gutov
2013-05-27 20:18             ` Roland Winkler
2013-05-28  5:32               ` Ulrich Mueller
2013-05-28  7:49                 ` Roland Winkler
2013-05-28 12:34                 ` Stefan Monnier
2013-05-27 20:59           ` Stefan Monnier
     [not found] ` <87obbvwgw6.fsf@sbs.ch>
2013-05-28 21:23   ` Roland Winkler
2013-05-28 22:29     ` Stefan Monnier
2013-05-29 13:27       ` Roland Winkler
2013-05-29 16:45       ` Ulrich Mueller
2013-05-29 22:29         ` Stefan Monnier
2013-05-30  7:14           ` Roland Winkler
2013-05-30  7:57             ` Jambunathan K
2013-05-30  8:04             ` Stephen J. Turnbull [this message]
2013-05-30 11:16               ` Roland Winkler
2013-05-30 17:25                 ` Stephen J. Turnbull
2013-05-30 17:55                   ` Stephen J. Turnbull
2013-05-30 18:22                     ` Eli Zaretskii
2013-05-30 20:47                       ` Andreas Schwab
2013-05-31  3:50                       ` Stephen J. Turnbull
2013-05-31 14:14                         ` Tom Tromey
2013-05-31 18:30                           ` Stephen J. Turnbull
2013-05-31 14:42                         ` Ted Zlatanov
2013-05-30  9:37           ` Ulrich Mueller
2013-05-30 11:24             ` Roland Winkler
2013-05-30 12:48               ` Ulrich Mueller
2013-05-30 14:57               ` Ted Zlatanov
2013-05-30 17:11                 ` Stefan Monnier
2013-05-30 20:31                   ` Ted Zlatanov
2013-05-30 14:37             ` Stefan Monnier
2013-05-30 15:03             ` Ted Zlatanov
2013-06-01 14:34         ` Steinar Bang

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=878v2wdhaz.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=christian.egli@sbs.ch \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=ulm@gentoo.org \
    --cc=winkler@gnu.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.