all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: defvar and "assignment to free variable" (was: Re: on specifying the C source code directory)
Date: Wed, 03 Feb 2016 00:04:40 +0100	[thread overview]
Message-ID: <87vb667lyv.fsf_-_@debian.uxu> (raw)
In-Reply-To: 8737tbh8xh.fsf@mbork.pl

Marcin Borkowski <mbork@mbork.pl> writes:

> As the docstring says, in Unix this is so.
> I don't know about other systems.

Me neither :)

>> (defvar find-function-C-source-directory)
>> (setq find-function-C-source-directory "~/.emacs.d/emacs-24.1/src")
>
> Out of curiosity: why defvar?

Without it, when I compile, it says:

    In toplevel form:
    help-new.el:11:7:Warning: assignment to free variable
        `find-function-C-source-directory'

`defvar' here is just used to communicate that you
will use the variable. Because that's exactly what
happens next, this isn't a hack. Really!

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2016-02-02 23:04 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 18:08 on ``An Introduction to Programming in Emacs Lisp'' Daniel Bastos
2016-01-28 23:58 ` Emanuel Berg
2016-01-29  2:11   ` Robert Thorpe
2016-01-29 12:38   ` Filipp Gunbin
2016-01-29 13:20     ` Paul Smith
2016-01-29 20:46     ` Emanuel Berg
2016-01-29 22:20       ` Marcin Borkowski
2016-01-30  9:05         ` Emanuel Berg
2016-01-30  9:57           ` Marcin Borkowski
2016-01-30  0:23       ` Robert Thorpe
2016-01-30  9:22         ` Emanuel Berg
2016-01-30 14:19           ` Robert Thorpe
2016-01-31 20:45             ` Emanuel Berg
2016-02-01 11:07               ` Marcin Borkowski
2016-02-02  0:28                 ` Emanuel Berg
2016-02-02  7:22                   ` Marcin Borkowski
2016-02-02 22:59                     ` Emanuel Berg
2016-02-03  9:25                       ` Marcin Borkowski
2016-02-03 20:00                         ` Emanuel Berg
2016-02-04 16:37                           ` Nick Dokos
     [not found]                         ` <mailman.3524.1454529667.843.help-gnu-emacs@gnu.org>
2016-02-03 20:12                           ` Pascal J. Bourguignon
2016-02-04  1:15                             ` Emanuel Berg
     [not found]                       ` <mailman.3489.1454491565.843.help-gnu-emacs@gnu.org>
2016-02-03 11:43                         ` Daniel Bastos
2016-02-03 20:08                           ` Emanuel Berg
     [not found]                   ` <mailman.3404.1454397765.843.help-gnu-emacs@gnu.org>
2016-02-02 11:43                     ` Rusi
     [not found]               ` <mailman.3321.1454324852.843.help-gnu-emacs@gnu.org>
2016-02-01 12:07                 ` on specifying the C source code directory (Was: Re: on ``An Introduction to Programming in Emacs Lisp'') Daniel Bastos
2016-02-01 12:38                   ` Marcin Borkowski
2016-02-01 12:32                     ` tomas
2016-02-01 13:54                       ` Kaushal Modi
2016-02-01 16:42                         ` on specifying the C source code directory Daniel Bastos
2016-02-02  0:17                           ` Emanuel Berg
2016-02-02  7:23                             ` Marcin Borkowski
2016-02-02 23:04                               ` Emanuel Berg [this message]
     [not found]                     ` <mailman.3326.1454332068.843.help-gnu-emacs@gnu.org>
2016-02-02 11:57                       ` Daniel Bastos
2016-02-02 11:52                         ` tomas
     [not found]       ` <mailman.3168.1454113433.843.help-gnu-emacs@gnu.org>
2016-01-30  3:20         ` on ``An Introduction to Programming in Emacs Lisp'' Rusi
     [not found] ` <mailman.3104.1454025553.843.help-gnu-emacs@gnu.org>
2016-01-29 20:29   ` Javier
2016-01-30  3:26   ` Pascal J. Bourguignon
2016-01-30  9:02     ` Emanuel Berg
2016-01-30 15:29 ` Eli Zaretskii

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=87vb667lyv.fsf_-_@debian.uxu \
    --to=embe8573@student.uu.se \
    --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.