all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Van L <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: missing src/ directory for eval.c
Date: Tue, 12 Feb 2019 23:21:29 +1100	[thread overview]
Message-ID: <m21s4dnqnq.fsf@scratch.space> (raw)
In-Reply-To: 86wom5x460.fsf@zoho.eu


> I don’t know if it is elite or dumbing down
> to put a tool tip kind of thing or brief text
> overlay to say how to get the missing
> documentation or missing source code.

The tool tip hints at you whilst inside
of GNU/Emacs on discovery of missing src
or doc, and getting either is as easy as
choosing an ELPA/MELPA package on a
click.

The platform packaging tools offer
emacs-full to include src, doc.

And, emacs-nano is the tiny stripped
down racing car installation that can
grow as an option.

-- 
© 2019 Van L
gpg using EEF2 37E9 3840 0D5D 9183  251E 9830 384E 9683 B835
"What's so strange when you know that you're a Wizard at 3?" -Joni Mitchell




      reply	other threads:[~2019-02-12 12:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 11:35 missing src/ directory for eval.c (Was: 1L?) Van Ly
2019-02-11 13:03 ` tomas
2019-02-11 13:56   ` Noam Postavsky
2019-02-11 14:13 ` missing src/ directory for eval.c Stefan Monnier
2019-02-11 15:16   ` Michael Albinus
2019-02-11 16:44     ` tomas
2019-02-11 20:51   ` Robert Thorpe
2019-02-11 20:54     ` Emanuel Berg
2019-02-11 22:11     ` Stefan Monnier
2019-02-12  0:01       ` Emanuel Berg
2019-02-12  4:00         ` Stefan Monnier
2019-02-12  5:16           ` Emanuel Berg
2019-02-11 14:17 ` missing src/ directory for eval.c (Was: 1L?) Yuri Khan
2019-02-11 20:45   ` Emanuel Berg
2019-02-11 22:01   ` Van L
2019-02-12  0:04     ` Emanuel Berg
2019-02-12 12:21       ` Van L [this message]

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=m21s4dnqnq.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.