Re: comint.el: EMACS environment variable

[Jae-hyeon Park]

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
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

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

[Zhang Wei]

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 following dialog bumped up again and again:



emacs-bootstrap-error.png
Description: PNG image

attach gdb gives something like this:

--8<---cut here---start->8---
C:\>gdb -p 15292
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Attaching to process 15292
[Switching to thread 15292.0x4164]
(gdb) bt
#0  0x7c921231 in ?? ()
(gdb) where
#0  0x7c921231 in ?? ()
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to thread 15292.0x3b68]
0x7c921231 in ?? ()
(gdb)
Continuing.

Program exited with code 02.
(gdb) q

C:\>--8<---cut here---end--->8---
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

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

[Andreas Seltenreich]

[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 ().

> Also, observing repeated hitting of g (gnus-group-get-new-news) with tcpflow
> shows that the same request and the same response are exchanged, with
> _no use of If-modified-since_ etc. traffic reducing features!

With mm-url-use-external set to nil, you could use the url package's
caching feature to minimize traffic (M-x customize-group RET url-cache RET).
It will then send proper If-modified-since headers.

regards,
andreas


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Re: problems building on OSF1

[Anselm Helbig]

> > 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 for your system if we
> aren't sure that the problem is indeed with all such systems, not
> specific to your machine.

The sysadmin says that they applied official patches and some "manual
bugfixes". The definitions of uint16_t (I supplied that manually) and
sockaddr_in6 are missing. I will investigate this further.

Additionally, I tested emacs on an updated system running Digital Unix
V5.1A and it compiled flawlessly with the native cc. IPv6 _and_
dumping were fine!

> >   (gdb) break Fsignal
> >   Breakpoint 2 at 0x1201c7cbc: file eval.c, line 1622.
> >   (gdb) run -batch -l loadup dump
> >   Starting program: 
> > /amd/molgix/4/home/abt_lh/helbig/compile/tru64/emacs-22.0.90/src/temacs 
> > -batch -l loadup dump
> >   Loading loadup.el (source)...
> >   Using load-path (/home/helbig/compile/tru64/emacs-22.0.90/lisp)
> >   Loading emacs-lisp/byte-run...
> >   Loading emacs-lisp/backquote...
> >   Loading subr...
> >   Symbol's value as variable is void: nil
> > 
> >   Program exited with code 0377.
> >   You can't do that without a process to debug.
> >   (gdb) 
> 
> How about if you put breakpoints in both `message' and `message3',
> does any of them break?  

No, they don't. 8-(



___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Re: comint.el: EMACS environment variable

[Chong Yidong]

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 filename of Emacs if we introduce an
INSIDE_EMACS variable.

Everyone else looks OK.


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

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

[Markus Triska]

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 vi-waves ()
  (interactive)
  (setq ol (make-overlay (point-min) (point-max) (current-buffer) t t))
  (overlay-put ol 'after-string "\n~\n~\n~\n~\n~\n~"))

And do M-x vi-waves (repeatedly for more of them). Bind it to a key:
  
(global-set-key [f9] 'vi-waves)

or add it to a hook to enable it whenever you want.


All the best!
Markus Triska


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Re: comint.el: EMACS environment variable

[Kim F. Storm]

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 
(list "TERM=emacs"
  (format "TERMCAP=emacs:co#%d:tc=unknown:" (window-width
  (unless (getenv "EMACS")
!   (list (concat "EMACS=" invocation-directory invocation-name)))
  process-environment))
(default-directory
  (if (file-accessible-directory-p default-directory)
--- 769,778 
(list "TERM=emacs"
  (format "TERMCAP=emacs:co#%d:tc=unknown:" (window-width
  (unless (getenv "EMACS")
!   ;; This is for Emacs 23:
!   ;; (list (concat "EMACS=" invocation-directory invocation-name))
!   (list "EMACS=t"))
! (list "INSIDE_EMACS=t")
  process-environment))
(default-directory
  (if (file-accessible-directory-p default-directory)

*** compile.el  11 Nov 2006 23:17:37 +0100  1.411
--- compile.el  17 Nov 2006 15:52:53 +0100
***
*** 1069,1075 
  ;; Set the EMACS variable, but
  ;; don't override users' setting of $EMACS.
  (unless (getenv "EMACS")
!   (list (concat "EMACS=" invocation-directory invocation-name)))
  (copy-sequence process-environment
(set (make-local-variable 'compilation-arguments)
 (list command mode name-function highlight-regexp))
--- 1069,1078 
  ;; Set the EMACS variable, but
  ;; don't override users' setting of $EMACS.
  (unless (getenv "EMACS")
!   ;; This is for Emacs 23:
!   ;; (list (concat "EMACS=" invocation-directory invocation-name))
!   '("EMACS=t"))
! '("INSIDE_EMACS=t")
  (copy-sequence process-environment
(set (make-local-variable 'compilation-arguments)
 (list command mode name-function highlight-regexp))


*** misc.texi   12 Sep 2006 23:49:59 +0200  1.93
--- misc.texi   17 Nov 2006 17:16:03 +0100  
***
*** 486,497 
  @kbd{C-x @key{RET} p} in the shell buffer.  @xref{Communication
  Coding}.
  
  @cindex @env{EMACS} environment variable
Unless the environment variable @env{EMACS} is already defined,
! Emacs defines it in the subshell, with value equal to Emacs's absolute
! file name.  A shell script
! can check this variable to determine whether it has been run from an
! Emacs subshell.
  
  @node Shell Mode
  @subsection Shell Mode
--- 486,507 
  @kbd{C-x @key{RET} p} in the shell buffer.  @xref{Communication
  Coding}.
  
+ @cindex @env{INSIDE_EMACS} environment variable
+   Emacs unconditionally defines the environment variable
+ @env{INSIDE_EMACS} in the subshell, with value @code{t}.  A shell
+ script can check this variable to determine whether it has been run
+ from an Emacs subshell.  This variable is new in Emacs 22, and
+ supersedes the @env{EMACS} environment variable.
+ 
  @cindex @env{EMACS} environment variable
Unless the environment variable @env{EMACS} is already defined,
! Emacs defines it in the subshell, with value @code{t}.
! 
! @strong{Warning:} Checking this variable to test whether a shell
! script is being run inside Emacs is deprecated, and from Emacs 23 its
! value will change to be equal to Emacs's absolute file name.  New and
! existing programs should be changed to check @env{INSIDE_EMACS} before
! @env{EMACS}.
  
  @node Shell Mode
  @subsection Shell Mode

*** NEWS15 Nov 2006 13:44:34 +0100  1.1405
--- NEWS17 Nov 2006 17:21:19 +0100  
***
*** 1455,1462 
  but declared obsolete.
  
  +++
! *** The EMACS environment variable now defaults to Emacs's absolute
! file name, instead of to "t".
  
  ** M-x Compile changes:
  
--- 1455,1466 
  but declared obsolete.
  
  +++
! *** The new INSIDE_EMACS environment variable is set unconditionally
! to the value "t".  It supersedes the EMACS environment variable, which
! is planned to change value to Emacs's absolute file name in Emacs 23.
! 
! Programs that need to know whether they are started inside Emacs,
! should check INSIDE_EMACS before checking EMACS.
  
  ** M-x Compile changes:
  

--
Kim F. Storm <[EMAIL PROTECTED]> http://www.cua.dk



___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Re: comint.el: EMACS environment variable

[Kim F. Storm]

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



___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Re: comint.el: EMACS environment variable

[Richard Stallman]

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 configure scripts are following a general
convention for configuration files.  The convention is not stated
explicitly, but it is implicit in this part of standards.texi:

Specifying variables as arguments to @code{configure}, like this:
@example
./configure CC=gcc
@end example
is preferable to setting them in environment variables:
@example
CC=gcc ./configure
@end example
as it helps to recreate the same configuration later with
@file{config.status}.
@end table

We cannot criticize them for using EMACS to specify where to find
Emacs after we suggested using CC to specify where to find cc.

So I think the only correct solution in the long term is to move to a
different variable (such as INSIDE_EMACS) to say "you're inside
Emacs".  This means we should start setting the other envvar now.

There are two ways to do the transition: with EMACS=t or with
EMACS=<>.  When we changed it to <>, we
thought that would be upward compatible.  Since it is not,
it means that for the short term we have to choose between one
set of bugs and another.

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.


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

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

[Chong Yidong]

Eli Zaretskii <[EMAIL PROTECTED]> writes:

>> yow is an interactive compiled Lisp function in `yow.el'.
>> It is bound to.
>> 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 remove it
from the menu bar, since Yow has been pretty much gutted due to legal
reasons.



___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

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

[Jan Djärv]

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 (do_ewmh_fullscreen): Declare variable before XSETFRAME
to avoid gcc 2.96 error.

%%%
diff -c -r1.931 xterm.c
*** src/xterm.c 10 Nov 2006 08:00:47 -  1.931
--- src/xterm.c 17 Nov 2006 05:08:57 -
***
*** 8333,8345 
if (have_net_atom) 
  {

Lisp_Object frame;
-   XSETFRAME (frame, f);
const char *atom = "_NET_WM_STATE";
const char *fs = "_NET_WM_STATE_FULLSCREEN";
const char *fw = "_NET_WM_STATE_MAXIMIZED_HORZ";
const char *fh = "_NET_WM_STATE_MAXIMIZED_VERT";
const char *what = NULL;
  
/* If there are _NET_ atoms we assume we have extended window manager

   hints.  */
switch (f->want_fullscreen) 
--- 8333,8346 
if (have_net_atom) 
  {

Lisp_Object frame;
const char *atom = "_NET_WM_STATE";
const char *fs = "_NET_WM_STATE_FULLSCREEN";
const char *fw = "_NET_WM_STATE_MAXIMIZED_HORZ";
const char *fh = "_NET_WM_STATE_MAXIMIZED_VERT";
const char *what = NULL;
  
+   XSETFRAME (frame, f);
+ 
/* If there are _NET_ atoms we assume we have extended window manager

   hints.  */
switch (f->want_fullscreen) 
%%%






___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

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

[Eli Zaretskii]

> 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.
> No it isn't. I see others there, but not yow.

Thanks, I will look into this bug.

> (yow &optional insert display)
> 
> Return or display a random Zippy quotation.  With prefix arg,
> insert it.
> (yow)"Yow!  Legally-imposed CULTURE-reduction is CABBAGE-BRAINED!"
> (yow)"Yow!  Legally-imposed CULTURE-reduction is CABBAGE-BRAINED!"
> And it's not random anymore either.

That's because the file yow.lines has only one line.  So yow
_randomly_ chooses the same line ;-)


___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug