From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: BBDB v3 approaching release
Date: Thu, 30 May 2013 10:57:32 -0400 [thread overview]
Message-ID: <87k3mg7bxf.fsf@lifelogs.com> (raw)
In-Reply-To: 20903.14080.45049.893441@gargle.gargle.HOWL
On Thu, 30 May 2013 13:24:48 +0200 "Roland Winkler" <winkler@gnu.org> wrote:
RW> On Thu May 30 2013 Ulrich Mueller wrote:
>> Emacs itself uses a different layout and keeps non-lisp files in
>> different directories like etc or info. (Hopefully there are no plans
>> to change that?)
RW> The problem is really that the TeX files generated by bbdb-print
RW> connect two different worlds:
RW> The TeX file is generated by emacs that comes with its search path
RW> and installation tree. But then this TeX file gets compiled by the
RW> TeX command that only knows its own search paths.
RW> And all this happens in a user directory so that everything should
RW> not depend on the absolute directories used by the particular
RW> installations of emacs and TeX.
This may be quite heretical, but have you considered Markdown for the
BBDB docs? No build systems needed; readable as plain text; convertible
to many other formats with little work; really easy to learn and use.
Emacs can view it. I've been happy with Markdown for personal and work
use.
The lack of a build system is especially appealing, from experience with
installing hundreds of megabytes for the documentation support toolchain
for Gnus and BBDB.
Ted
next prev parent reply other threads:[~2013-05-30 14:57 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
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 [this message]
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
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=87k3mg7bxf.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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 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).