Aidan Kehoe <kehoea(a)parhasard.net> wrote:
> […]
> So I tried:
> | make EMACSDEBUGPATHS=yes BATCH='-no-packages -batch -eval
"(setq user-mail-address \"mockbuild(a)fedoraproject.org\")"'
> but that fails with:
> | ./temacs -nd -no-packages -batch -eval "(setq
> | user-mail-address \"mockbuild(a)fedoraproject.org\")" -l
> | /builddir/build/BUILD/xemacs-beta/src/../lisp/update-elc.el
> | temacs can only be run in -batch mode.
> What options are supported by temacs that could be used to
> set user-mail-address?
What you’ve done is reasonable, as far as I can see it’s a bug in the
temacs
code that it handles -eval badly there.
I'm not sure that's a bug per se—temacs has a pretty limited
use case, and it works fine for that AFAICT.
> (My fallback solution is to directly patch
> lisp/update-elc{,-2}.el, but I'd prefer to resolve the issue
> at make level if possible.)
What’s your concern with patching Lisp? You worry that it’s less
maintainable?
Fedora, like other distributions, recommends upstreaming all
patches (which is reasonable to me), but that also means
that patches must be useful for a wider audience which in
this case collides with the fact that setting the compiling
user's mail address is a rather niche endeavour :-). So one
would probably have to teach temacs to support -eval which
is a big solution for a small problem.
Also, if lisp/update-elc{,-2}.el were patched, those changes
would have to be "reverted" before those files are installed
in /usr/share/xemacs-* (therefore, on second thought, it
would probably make more sense to have another file setting
user-mail-address and then have temacs load that as well
with "-l set-user-mail-address.el"). Setting
user-mail-address on the command line would make that whole
process simpler and easier to understand. (Maybe I'm just a
fan of let :-).)
> P. S.: I tried to subscribe first to this mailing list via
>
https://lists.xemacs.org/, but the link in the "Con-
> firmation needed" mail redirects to
>
https://lists.xemacs.org/users/address_activation/[40-hex-string]/
> and then gives a "Server Error (500)", with the sub-
> scription request lingering in "pending" state.
Partially sorted, sorry about the delay!
No problem; heads up: I just sent a subscription request for
xemacs-patches :-).
Tim