From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: require-hard-newlines to use newline Date: Tue, 08 Mar 2005 14:02:04 -0500 Message-ID: References: <1483.220.255.172.231.1109730379.squirrel@www.stupidchicken.com> <200503020302.j2232fR21722@raven.dms.auburn.edu> <2750.220.255.172.231.1109734015.squirrel@www.stupidchicken.com> <1415.220.255.169.59.1109818150.squirrel@www.stupidchicken.com> <1404.220.255.169.59.1109889146.squirrel@www.stupidchicken.com> <200503040033.j240XD022473@raven.dms.auburn.edu> <50554.203.116.59.23.1109897782.squirrel@www.stupidchicken.com> <200503080005.j2805Kg28696@raven.dms.auburn.edu> <1057.220.255.169.59.1110247845.squirrel@www.stupidchicken.com> <200503080428.j284SD928952@raven.dms.auburn.edu> <200503081545.j28FjAV29254@raven.dms.auburn.edu> <2462.220.255.169.59.1110300154.squirrel@www.stupidchicken.com> In-Reply-To: <200503081812.j28ICcJ00917@raven.dms.auburn.edu> (Luc Teirlinck's message of "Tue, 8 Mar 2005 12:12:38 -0600 (CST)") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.817, requis 5, autolearn=not spam, AWL 0.08, BAYES_00 -4.90) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: news.gmane.org gmane.emacs.devel:34336 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34336 > Maybe it's because you call M-x byte-compiler from an Emacs where longlines > was already loaded. > I do not believe so: > [bash2.05b.0 ~ 3 1] emacs-22.0.50 -batch -f batch-byte-compile > longlines.el > Wrote /home/teirllm/longlines.elc > [bash2.05b.0 ~ 3 2] > Maybe it is because all the offending occurrences of the variable are > in defadvice forms. Indeed. The code in defadvice is (generally) not compiled during byte-compilation. > Another thing I do not understand is that (devar longlines-mode) did > not help. Only (devar longlines-mode nil) did. A (defvar longlines-mode) doesn't have any long term effect: it only temporarily tells the byte-compiler to shut up. This only lasts until the file is byte-compiled. If you do further byte-compilation (e.g. of the advice code or of code output by some macro), the byte-compiler won't remember that the file where this code originally appeared had a (defvar longlines-mode). Stefan