Re: 1L?

[Van L]

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