From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: winkler@gnu.org, emacs-devel@gnu.org
Subject: Re: BBDB v3 approaching release
Date: Fri, 31 May 2013 12:50:51 +0900 [thread overview]
Message-ID: <87y5avbyec.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <83ppw849bq.fsf@gnu.org>
Eli Zaretskii writes:
> > From: "Stephen J. Turnbull" <stephen@xemacs.org>
> > Date: Fri, 31 May 2013 02:55:49 +0900
> >
> > Ah, I didn't know what bbdb-print does.
> >
> > Now that I do, I don't see what's so hard about
> >
> > (shell-command (format "TEXINPUTS=%s%s tex %s"
> > (bbdb-style-file-directory)
> > (getenv "TEXINPUTS")
> > file-to-tex))
>
> That it only works with a Posixy shell?
Last I heard Emacs doesn't have a policy that says that's a
showstopper, although it won't stop you from fixing it if you like.
Anyway, I'm sure there's a way to work around it with enough effort.
I'm just not going to make it. The code above is proof of concept,
not a patch submission to Emacs (or BBDB for that matter).
The practical deal-breaker for "install in the right place" is that
Emacs doesn't "own" the texmf hierarchies, so you can't guarantee that
ELPA can install those sources "where they belong" according to
tradition or FHS. Given that, I don't see why anybody should care
where they are installed, as long as BBDB can find them.
Ted Z's proposal for enhancing ELPA packages' ability to find their
stuff is a first step in the right direction, I think. But AFAIK
there is no spec for *user* FHS. Python has been playing around with
~/.local among others (I think that may be an fd.o draft standard or
something?) If that were to become widespread, you could add ~/.local
to your kpathsea path, and that would be a big win. Failing that (ie,
for the foreseeable future), I think what ELPA should do is provide a
suite of functions for finding package resources such as elisp
(installed), the source tree, graphics and other multimedia, helper
files for external apps (eg, the bbdb-print TeX style files), helper
executables, and so on.
next prev parent reply other threads:[~2013-05-31 3:50 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 [this message]
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=87y5avbyec.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.