all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 32893@debbugs.gnu.org, npostavs@gmail.com
Subject: bug#32893: describe-variable doesn't metion what lisp file created the variable
Date: Mon, 01 Oct 2018 16:43:27 +0300	[thread overview]
Message-ID: <834le54wao.fsf@gnu.org> (raw)
In-Reply-To: <878t3hrf0b.fsf@jidanni.org>

> From: 積丹尼 Dan Jacobson
> 	<jidanni@jidanni.org>
> Date: Mon, 01 Oct 2018 21:08:20 +0800
> Cc: 32893@debbugs.gnu.org
> 
> I get:
> 
> abbrev-file-name’s value is "~/.emacs.d/abbrev_defs"
> 
> Documentation:
> Default name of file from which to read abbrevs.
> 
> You can customize this variable.
> 
> [back]
> 
> emacs-version is a variable defined in ‘C source code’.
> Its value is "25.2.2"
> 
> Hmmm, at least that last one worked, here on Debian.

Maybe you should report this to Debian, because my Emacs 25.2 does
show the file where abbrev-file-name is defined.





  parent reply	other threads:[~2018-10-01 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r2h9ahig.fsf@tethera.net>
     [not found] ` <87tvm5pye2.fsf@jidanni.org>
     [not found]   ` <handler.910021.D910021.153840454221352.notifdone@bugs.debian.org>
2018-10-01 12:44     ` bug#32893: describe-variable doesn't metion what lisp file created the variable 積丹尼 Dan Jacobson
2018-10-01 12:51       ` Noam Postavsky
2018-10-01 13:08         ` 積丹尼 Dan Jacobson
2018-10-01 13:41           ` Noam Postavsky
2018-10-01 14:13             ` 積丹尼 Dan Jacobson
2018-10-01 13:43           ` Eli Zaretskii [this message]
2018-10-01 21:46       ` bug#32893: Let him know source code is available 積丹尼 Dan Jacobson
2018-10-01 22:56         ` Glenn Morris
2018-10-01 23:04           ` Glenn Morris
2018-10-02  0:28       ` bug#32893: GNU wishes Debian not split out .els anymore 積丹尼 Dan Jacobson

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=834le54wao.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32893@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=npostavs@gmail.com \
    /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.