From: Van L <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: 1L?
Date: Sun, 10 Feb 2019 17:34:33 +1100 [thread overview]
Message-ID: <m2lg2oup6u.fsf@scratch.space> (raw)
In-Reply-To: 20190208092717.GA4663@tuxteam.de
tomas writes:
>
> That said, the Emacs docs /are/ available for Debianites, under
> the non-free section. Where's the problem?
>
There's less of a problem if GNU/Emacs
can discover the documentation is
missing and describes the 'non-free'
steps to follow. I don't use Debian :-)
Maybe GnuSense doesn't have the problem
at all.
>> On NetBSD the Emacs package is difficult, cross referencing to the C
>> source code is too hard.
>
> What do you mean by that?
>
If I look up the documentation for
'eval' function, it says
eval is a built-in function in ‘C source code’.
I get a dialog box on clicking the
'C source code'.
I list the contents installed and find
there's no src/ directory provided by
the NetBSD pkg_add installer.
MacPorts also does not provide the
src/ directory in the emacs-mac-app,
emacs-devel packages.
Previously, when I was building GNU/Emacs directly
from src the click on 'C source code' just worked.
I now have in the .emacs:
(if (version< emacs-version "27.0.50")
(progn
(package-initialize)
(setq source-directory "~/opt/share/src/emacs-26.1/src"))
(setq source-directory "~/opt/share/src/emacs/src"))
the src/ directory is a 'git clone'
covering for what's missing in from the
installers. Those are *not* the C source
files the package installer actually
used.
How should the .emacs file be structured
to simultaneously work with 26 and 27's
M-x customize?
Thanks.
--
© 2019 Van L
gpg using EEF2 37E9 3840 0D5D 9183 251E 9830 384E 9683 B835
"What is connectivity?" -John Sculley
next prev parent reply other threads:[~2019-02-10 6:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 2:05 Suggestions for 1L computer to run Emacs 2019 Van L
2019-02-03 13:21 ` Stefan Monnier
2019-02-05 1:00 ` Van L
2019-02-06 15:06 ` Stefan Monnier
2019-02-09 1:58 ` Van L
2019-02-09 3:07 ` Emanuel Berg
2019-02-11 13:18 ` Van L
2019-02-11 20:31 ` Emanuel Berg
2019-02-12 12:37 ` [*OFF-TOPIC*] " Van L
2019-02-09 13:28 ` Stefan Monnier
2019-02-09 20:29 ` Emanuel Berg
2019-02-10 14:54 ` [OFFTOPIC] " Stefan Monnier
2019-02-10 15:03 ` 조성빈
2019-02-10 18:14 ` Stefan Monnier
2019-02-10 20:26 ` Emanuel Berg
2019-02-06 15:38 ` 1L? (was: Suggestions for 1L computer to run Emacs 2019) Skip Montanaro
2019-02-06 16:31 ` 1L? Stefan Monnier
2019-02-06 16:50 ` 1L? Emanuel Berg
2019-02-07 10:31 ` 1L? Van L
2019-02-07 10:58 ` 1L? 조성빈
2019-02-07 15:47 ` 1L? Emanuel Berg
2019-02-07 16:38 ` 1L? 조성빈
2019-02-07 19:51 ` 1L? Emanuel Berg
2019-02-08 2:27 ` 1L? 조성빈
2019-02-08 15:02 ` 1L? Emanuel Berg
2019-02-08 6:16 ` 1L? Vladimir Sedach
2019-02-08 22:55 ` 1L? Emanuel Berg
2019-02-08 8:46 ` 1L? Van L
2019-02-08 15:03 ` 1L? Emanuel Berg
2019-02-07 15:42 ` 1L? Emanuel Berg
2019-02-08 9:14 ` 1L? Van L
2019-02-08 9:27 ` 1L? tomas
2019-02-08 15:15 ` 1L? Emanuel Berg
2019-02-08 15:39 ` 1L? tomas
2019-02-10 6:34 ` Van L [this message]
2019-02-10 8:11 ` 1L? tomas
2019-02-10 20:24 ` 1L? Emanuel Berg
2019-02-10 20:21 ` 1L? Emanuel Berg
2019-02-08 15:10 ` 1L? Stefan Monnier
2019-02-08 15:10 ` 1L? Emanuel Berg
2019-02-10 15:02 ` [OFFTOPIC] 1L? Stefan Monnier
2019-02-10 15:34 ` Richard Melville
2019-02-11 19:48 ` Stefan Monnier
2019-02-12 3:48 ` Vladimir Sedach
2019-02-10 20:27 ` Emanuel Berg
2019-02-12 4:31 ` Xavier Maillard
2019-02-12 5:19 ` Emanuel Berg
2019-02-14 11:10 ` Van L
2019-02-15 18:49 ` Xavier Maillard
2019-02-12 18:35 ` Steinar Bang
2019-02-12 22:23 ` Emanuel Berg
2019-02-13 20:34 ` Stefan Monnier
2019-02-14 8:34 ` tomas
2019-02-16 7:58 ` Steinar Bang
2019-02-08 15:07 ` 1L? Stefan Monnier
2019-02-15 10:06 ` 1L? Van L
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=m2lg2oup6u.fsf@scratch.space \
--to=van@scratch.space \
--cc=help-gnu-emacs@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.