Re: (yow) just gives the same line every time

From: Dan Jacobson [EMAIL PROTECTED] Date: Fri, 17 Nov 2006 00:32:33 +0800 yow is an interactive compiled Lisp function in `yow.el'. It is bound to menu-bar tools games yow. No it isn't. I see others there, but not yow. Thanks, I will look into this bug. (yow optional insert

Re: Patch: src/xterm.c for old C compiler

Tetsurou Okazaki skrev: Hi, My environment, gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-98), requires the following patch to build CVS-head Emacs again. Please apply this. Applied. Jan D. 2006-11-17 Tetsurou Okazaki [EMAIL PROTECTED] (tiny change) * xterm.c

Re: (yow) just gives the same line every time

Eli Zaretskii [EMAIL PROTECTED] writes: yow is an interactive compiled Lisp function in `yow.el'. It is bound to menu-bar tools games yow. No it isn't. I see others there, but not yow. Thanks, I will look into this bug. It's there --- under Random quotation. I think we should

Re: comint.el: EMACS environment variable

IIUC, the problem that triggered the change from EMACS=t to EMACS=/where/is/emacs was that some configure scripts (unrelated to Emacs) assumed that the environment variable EMACS -- if set -- contains the full directory file name of the Emacs executable. I think that these

Re: comint.el: EMACS environment variable

Richard Stallman [EMAIL PROTECTED] writes: So let's set both EMACS and INSIDE_EMACS to t. Fine with me! Then all current users of EMACS=t will have time to adapt to the change ... before Emacs 23 is out. -- Kim F. Storm [EMAIL PROTECTED] http://www.cua.dk

Re: comint.el: EMACS environment variable

Richard Stallman [EMAIL PROTECTED] writes: I think we will have fewer bugs if we put EMACS back to t. So let's set both EMACS and INSIDE_EMACS to t. Here is a patch: *** comint.el 29 Sep 2006 10:48:53 +0200 1.348 --- comint.el 17 Nov 2006 16:43:23 +0100 *** *** 769,775

Re: emacs -nw vs. default-indicate-empty-lines

Dan Jacobson [EMAIL PROTECTED] writes: I'm saying there should be some variable the user can toggle to get those ~ below that are the default in vi(1) and less(1). ~ ~ ~ Evaluate the expressions I posted using M-: (M-x eval-expression), and you get that. Or put this in .emacs: (defun

Re: comint.el: EMACS environment variable

Looks fine to me, except ! ;; This is for Emacs 23: ! ;; (list (concat EMACS= invocation-directory invocation-name)) ! '(EMACS=t)) ! '(INSIDE_EMACS=t) The comment is incorrect, and should simply be removed: we won't be changing EMACS to the

Re: problems building on OSF1

Sorry for the delay and for messing up the threading, I'm afraid my spamfilter ate your last mail, Eli. Then perhaps you should be working on your spam filter ;-) It's on my todo-list. 8-) Maybe I should _really_ talk to our sysadmins... Yes, please do. I don't want to disable IPv6

Re: nnrss doesn't use If-modified-since

[I'm only following up to a subset of the issues] Dan Jacobson writes: Can you believe doing $ http_proxy=http://localhost:8080/ emacs-snapshot -f gnus causes GET http://localhosthttp://localhost:8080/ HTTP/1.1... or at least that is what tcpflow shows. AFAICT this has been fixed recently

emacs-unicode-2: bootstrap error on windows-xp

Configed like this: --8---cut here---start-8--- configure.bat --with-gcc --no-cygwin --no-opt make bootstrap --8---cut here---end---8--- During bootstrap emacs encounter fatal error when byte-compile some .el files, the

Re: comint.el: EMACS environment variable

What about the EMACS variable in term mode (the one invoked by M-x term RET)? Currently, the variable is set to the emacs version, like $ echo $EMACS 22.0.90.1 (term:0.96) Jae-hyeon ___ emacs-pretest-bug mailing list