From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: Evil defvars in org.el
Date: Sat, 28 Apr 2012 18:31:26 +0200 [thread overview]
Message-ID: <87vckj6co1.fsf@Rainer.invalid> (raw)
In-Reply-To: jwvy5pfdhbc.fsf-monnier+emacs@gnu.org
Stefan Monnier writes:
>> I had no idea this is even possible... and the manual advises that the
>> defvar should "usually be at top-level". So, commenting out all the
>> file-level (defvar date) in all of org and then changing in org-bbdb.el
>> like this:
>
> In general, having them at file-level is just as good as having it
> within a defun.
Either I've lost you here or the conclusion is that we can't do anything
in org to make these defvars less evil and should just silence the
warnings associated with them?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2012-04-28 16:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 3:17 Evil defvars in org.el Chong Yidong
2012-04-27 6:07 ` Bastien
2012-04-27 14:48 ` Bastien
2012-04-27 14:57 ` Edward Reingold
2012-04-27 16:14 ` Bastien
2012-04-27 17:09 ` SAKURAI Masashi
2012-04-27 16:05 ` Glenn Morris
2012-04-27 16:33 ` Drew Adams
2012-04-28 0:15 ` Miles Bader
2012-04-28 0:17 ` Drew Adams
2012-04-28 0:48 ` Miles Bader
2012-04-28 2:25 ` Chong Yidong
2012-05-04 6:56 ` Glenn Morris
2012-05-04 15:29 ` Stefan Monnier
2012-05-04 20:53 ` Johan Bockgård
2012-05-05 0:37 ` Stefan Monnier
2012-05-05 20:00 ` Glenn Morris
2012-05-07 14:57 ` Stefan Monnier
2012-04-28 2:14 ` Stefan Monnier
2012-04-28 5:57 ` Achim Gratz
2012-04-28 15:10 ` Stefan Monnier
2012-04-28 16:31 ` Achim Gratz [this message]
2012-04-28 19:33 ` Stefan Monnier
2012-04-28 6:00 ` Drew Adams
2012-05-08 22:48 ` Martyn Jago
2012-05-09 17:37 ` Stefan Monnier
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=87vckj6co1.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-devel@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.