Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM

2006-12-08 Thread Eli Zaretskii
 Date: Thu, 7 Dec 2006 23:55:58 -0800
 From: Deutsch, Will [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED],
   [EMAIL PROTECTED],
   emacs-pretest-bug@gnu.org
 
 I was specifically asked to provide the / vs \ output of Dir.

Sorry, I missed that.

Lennart, can you tell why you asked for that, and what does it have to
do with the original problem?


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


Re: GTK build crashes under X

2006-12-08 Thread Jan Djärv



Eli Zaretskii skrev:

Date: Fri, 08 Dec 2006 08:27:21 +0100
From: =?ISO-8859-1?Q?Jan_Dj=E4rv?= [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], emacs-pretest-bug@gnu.org

Alas, I couldn't find any documentation of the *.pc files' format, so
that I could edit the files.

It is in the man page for pkg-config.


What man page?  I'm quite sure I tried man pkg-config and didn't
find it there.


Hmm, there may be version differences.  Here is what my man-page says:




METADATA FILE SYNTAX
   To  add a library to the set of packages pkg-config knows about, simply
   install a .pc file. You should install this file to libdir/pkgconfig.


   Here is an example file:
   # This is a comment
   prefix=/home/hp/unst   # this defines a variable
   exec_prefix=${prefix}  # defining another variable in terms of the first
   libdir=${exec_prefix}/lib
   includedir=${prefix}/include

   Name: GObject# human-readable name
   Description: Object/type system for GLib # human-readable description
   Version: 1.3.1
   URL: http://www.gtk.org
   Requires: glib-2.0 = 1.3.1
   Conflicts: foobar = 4.5
   Libs: -L${libdir} -lgobject-1.3
   Libs.private: -lm
   Cflags: -I${includedir}/glib-2.0 -I${libdir}/glib/include


   You would normally generate the file using  configure,  of  course,  so
   that the prefix, etc. are set to the proper values.
   Files have two kinds of line: keyword lines start with a keyword plus a
   colon, and variable definitions start with an alphanumeric string  plus
   an  equals sign. Keywords are defined in advance and have special mean-
   ing to pkg-config; variables do not, you can have  any  variables  that
   you  wish  (however,  users  may expect to retrieve the usual directory
   name variables).


   Note that variable references are written ${foo}; you can escape lit-
   eral ${ as $${.


   Name:  This field should be a human-readable name for the package. Note
  that it is not the name passed as an argument to pkg-config.

   Description:
  This should be a brief description of the package

   URL:   An URL where people can get more information about and  download
  the package

   Version:
  This   should  be  the  most-specific-possible  package  version
  string.

   Requires:
  This is a comma-separated list of packages that are required  by
  your package. Flags from dependent packages will be merged in to
  the flags reported for your package. Optionally, you can specify
  the  version  of the required package (using the operators =, ,
  , =, =); specifying a version allows  pkg-config  to  perform
  extra  sanity  checks. You may only mention the same package one
  time on the Requires: line. If  the  version  of  a  package  is
  unspecified, any version will be used with no checking.

   Conflicts:
  This  optional line allows pkg-config to perform additional san-
  ity checks, primarily to detect broken user installations.   The
  syntax  is  the  same  as Requires: except that you can list the
  same package more than once here, for example foobar  =  1.2.3,
  foobar  = 1.2.5, foobar = 1.3, if you have reason to do so. If
  a version isn’t specified, then your package conflicts with  all
  versions  of the mentioned package.  If a user tries to use your
  package and a conflicting package at the same  time,  then  pkg-
  config will complain.

   Libs:  This  line  should give the link flags specific to your package.
  Don’t add any flags for required packages; pkg-config  will  add
  those automatically.


   Libs.private:
  This  line  should  list  any private libraries in use.  Private
  libraries are libraries  which  are  not  exposed  through  your
  library, but are needed in the case of static linking.


   Cflags:
  This  line  should list the compile flags specific to your pack-
  age.  Don’t add any flags for required packages; pkg-config will
  add those automatically.


Jan D.


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


Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM

2006-12-08 Thread Jason Rumney

Lennart Borgman wrote:

I know that it is important that many users build Emacs too, but the 
problem on MS Windows is that most users will not do that. That means 
that there will be fewer testers when we do not supply prebuilt binaries.
The aim of a pretest has always been to get a limited number of testers 
who are technically skilled enough to give us meaningful bug reports. 
What we don't want during pretest is a flood of vague bug reports from 
the masses, because we don't have the bandwidth to deal with that.




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


Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM

2006-12-08 Thread Juanma Barranquero

On 12/8/06, Eli Zaretskii [EMAIL PROTECTED] wrote:


I have no problems with having a precompiled Windows binary distro as
part of the pretest, as long as it is a straight compilation of the
pretest sources without any extra quirks.  If you are willing to do
this job, please talk to Chong Yidong and coordinate your uploads to
alpha.gnu.org.


I'm willing to build precompiled binaries for Windows (pretest, and
perhaps periodic builds from the CVS once the current release is out).
I'll talk with Chong Yidong (unless Lennart prefers to do it himself).

   /L/e/k/t/u


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


Re: bad copyright years

2006-12-08 Thread Eli Zaretskii
I don't understand this change:

Index: config.bat
===
RCS file: /cvsroot/emacs/emacs/config.bat,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- config.bat  20 Apr 2006 06:59:37 -  1.42
+++ config.bat  5 Dec 2006 05:36:19 -   1.43
@@ -1,8 +1,8 @@
 @echo off
 rem   
--
 rem   Configuration script for MSDOS
-rem   Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2001, 2004, 2006
-rem   Free Software Foundation, Inc.
+rem   Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2001, 2002, 2003
+rem   2004, 2005, 2006  Free Software Foundation, Inc.

 rem   This file is part of GNU Emacs.

There's not a single change that has been done in config.bat in the
years 2003 and 2005.  maintain.texi says (in node Copyright
Notices):

   To update the list of year numbers, add each year in which you have
made nontrivial changes to the package.

So why add to config.bat years that didn't see any changes in that
file?

Btw, why isn't this change reflected in ChangeLog?


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


Re: Directory name completion blocks when it shouldn't

2006-12-08 Thread Chris Moore
Richard Stallman [EMAIL PROTECTED] writes:

 On the other hand, cd does use read-directory-name.
 So this appears to be a bug in the completion routines themselves.

read-directory-name uses read-file-name with PREDICATE set to
'file-directory-p

read-file-name uses read-file-name-internal

read-file-name-internal ignores the value of PREDICATE if ACTION is
nil (ACTION is t if we are listing possible completions, and nil if
are actually doing the completion)

When we are doing the completion, read-file-name-internal calls
file_name_completion in dired.c to actually do it.
file_name_completion doesn't have any code to complete only
directories, but it does honour the value of
completion-ignored-extensions.  If we temporarily bind
completion-ignored-extensions to include the empty string, it will
ignore all files, but not directories.

So here's a possible fix:


--- lisp/files.el   2006-12-01 14:27:47.0 +0100
+++ /tmp/files.el   2006-12-08 15:49:50.0 +0100
@@ -576,11 +576,12 @@
 the value of `default-directory'.
   (unless dir
 (setq dir default-directory))
-  (read-file-name prompt dir (or default-dirname
-(if initial (expand-file-name initial dir)
-  dir))
- mustmatch initial
- 'file-directory-p))
+  (let ((completion-ignored-extensions (cons  
completion-ignored-extensions)))
+(read-file-name prompt dir (or default-dirname
+  (if initial (expand-file-name initial dir)
+dir))
+   mustmatch initial
+   'file-directory-p)))
 
 
 (defun pwd ()


And a test case:

$ mkdir -p /tmp/dir/subdir
$ touch /tmp/dir/sub.txt
$ emacs
M-x cd RET /tmp/dir/s TAB

Before applying the patch, TAB will complete only up to /tmp/dir/sub.  With
the patch it will complete to /tmp/dir/subdir/.


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


try-completion crashes on non-obarray vector

2006-12-08 Thread Johan Bockgård

try-completion may crash Emacs when given a non-obarray vector.

(try-completion  [])

=

Program received signal SIGSEGV, Segmentation fault.
0x004d7e67 in Ftry_completion (string=10456851, alist=9781604, 
predicate=9337233) at minibuf.c:1315
1315  if (XSYMBOL (bucket)-next)


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


Re: [Patch] build cvs emacs for x86_64-sun-solaris10

2006-12-08 Thread Chong Yidong
AKAJI Hiroyuki [EMAIL PROTECTED] writes:

 I successfully built cvs emacs on my Opteron box for the target
 x86_64-sun-solaris10.

Thanks, I've applied your patch to CVS, except for the following:

 --- src/fns.c 24 Nov 2006 19:53:56 -  1.422
 +++ src/fns.c 8 Dec 2006 04:14:20 -
 @@ -89,6 +89,8 @@
  #ifndef HAVE_UNISTD_H
  extern long time ();
  #endif
 +
 +static Lisp_Object concat (int, Lisp_Object *, enum Lisp_Type, int);
  
  DEFUN (identity, Fidentity, Sidentity, 1, 1, 0,
 doc: /* Return the argument unchanged.  */)

Why is this change needed?  The prototype for concat is defined later
in fns.c, on line 390:

#if __GNUC__
static Lisp_Object concat P_ ((int nargs, Lisp_Object *args, enum Lisp_Type 
target_type, int last_special)) __attribute__((noinline));
#else  /* !__GNUC__ */
static Lisp_Object concat P_ ((int nargs, Lisp_Object *args, enum Lisp_Type 
target_type, int last_special));
#endif

There is call to concat() between lines 89 and 390, so adding an extra
prototype at 89 should be a no-op.



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


doc strings of variable-at-point and find-variable

2006-12-08 Thread Drew Adams
These doc strings don't describe the position of the variable well:
The variable-at-point doc string mentions nothing about using a
variable near point - it says only around point, which suggests that
only a variable at point is used.  The find-variable doc string
mentions using a variable near point, but this suggests that the
nearest variable will be used, which is not always the case.

The actual variable used seems to be the one before or at point, even
if there is a closer one after point. I didn't check all cases, but
perhaps it would be more correct to say at or before point for both
doc strings.  Perhaps something also needs to be said about the
possible distance before point.


In GNU Emacs 22.0.50.1 (i386-msvc-nt5.1.2600)
 of 2006-07-19 on BOS-CTHEWLAP2
X server distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-msvc (12.00)'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENU
  locale-coding-system: cp1252
  default-enable-multibyte-characters: t




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


Re: bad copyright years

2006-12-08 Thread Glenn Morris
Eli Zaretskii wrote:

 There's not a single change that has been done in config.bat in the
 years 2003 and 2005.  maintain.texi says (in node Copyright
 Notices):

To update the list of year numbers, add each year in which
 you have made nontrivial changes to the package.

Changes to the _package_, not to the _file_.

 So why add to config.bat years that didn't see any changes in that
 file?

Because the Emacs package saw change in those years.

 Btw, why isn't this change reflected in ChangeLog?

To be honest, because the prospect of potentially writing ChangeLog
entries for 4000 files appalled me. These changes are all changes in
comments (essentially), which have no impact on how the code
performs.



PS Fun times ahead in 3 weeks when every single file in Emacs needs
2007 adding to the Copyright years...



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


M-x run-scheme failed to get start-file

2006-12-08 Thread Masayuki Ataka
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

1. I opened scheme file.
2. I typed `M-x run-scheme'
3. Error

Here's a *backtrack*.
A ChangeLog and a patch are added below.
I hope my patch help you.

Debugger entered--Lisp error: (void-variable progname)
  (concat ~/.emacs_ progname)
  (let ((progname ...) (start-file ...) (alt-start-file ...)) (if 
(file-exists-p start-file) start-file (and ... alt-start-file)))
  scheme-start-file(gosh)
  run-scheme(gosh -i)
  call-interactively(run-scheme)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)

--
Masayuki Ataka

2006-12-07  Masayuki Ataka  [EMAIL PROTECTED]

* cmuscheme.el (scheme-start-file): Use `let*', not `let'.

*** cmuscheme.el06 12 2006 19:28:23 +0900   1.44
--- cmuscheme.el08 12 2006 05:49:02 +0900   
***
*** 269,277 
Return the name of the start file corresponding to PROG.
  Search in the directories \~\ and \~/.emacs.d\, in this
  order.  Return nil if no start file found.
!   (let ((progname (file-name-nondirectory prog))
!   (start-file (concat ~/.emacs_ progname))
!   (alt-start-file (concat ~/.emacs.d/init_ progname .scm)))
  (if (file-exists-p start-file)
  start-file
(and (file-exists-p alt-start-file) alt-start-file
--- 269,277 
Return the name of the start file corresponding to PROG.
  Search in the directories \~\ and \~/.emacs.d\, in this
  order.  Return nil if no start file found.
!   (let* ((progname (file-name-nondirectory prog))
!(start-file (concat ~/.emacs_ progname))
!(alt-start-file (concat ~/.emacs.d/init_ progname .scm)))
  (if (file-exists-p start-file)
  start-file
(and (file-exists-p alt-start-file) alt-start-file

In GNU Emacs 22.0.91.4 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2006-12-06 on zack.beers.scphys.kyoto-u.ac.jp
X server distributor `The X.Org Foundation', version 11.0.6070
configured using `configure '--without-xim''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ja_JP.UTF-8
  locale-coding-system: utf-8
  default-enable-multibyte-characters: t

Major mode: Emacs-Lisp

Minor modes in effect:
  jabber-activity-mode: t
  iswitchb-mode: t
  auto-image-file-mode: t
  show-paren-mode: t
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
C-p C-p C-p C-p C-p C-x o C-f C-f C-f C-f C-f C-f C-f 
C-f C-f C-f C-f C-f C-f C-f C-f C-f C-f C-f C-f C-f 
C-f C-f C-f C-f C-f C-f C-b C-b C-b C-b C-d C-n C-d 
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n 
C-n C-n C-n C-n C-n C-n C-x o C-x C-g C-h i SPC u C-p 
C-p return SPC SPC C-x b return C-x b c u backspace 
m u return M-x r e p SPC SPC o r SPC e m SPC b u 
SPC SPC return

Recent messages:
Quit
Mark saved where search started [2 times]
Quit [3 times]
Making completion list...done
Making completion list...done
Can't find completion for diff-fl
Making completion list...done
-c
Making completion list... [2 times]
Loading emacsbug...done


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


using the first three buttons in the tool bar

2006-12-08 Thread Olivier Lecarme
I'm testing Emacs 22 on a Debian Sid PC installation.

I just tried the first three buttons in the tool bar, with some
difficulties. The same occurs with the first three entries in the File
menu. I have had no problem with C-x C-f or C-x C-d, which I normally
use. This explains why I'm discovering the problem after several days of
daily use.

The symptoms are various:

- first symptom:

 Xlib: unexpected async reply (sequence 0x210f)!
 
 (emacs:28050): Gdk-CRITICAL **: gdk_window_set_geometry_hints: assertion 
 `GDK_IS_WINDOW (window)' failed
 
 (emacs:28050): Gdk-CRITICAL **: gdk_window_move_resize: assertion 
 `GDK_IS_WINDOW (window)' failed

and Emacs hangs and must be killed.

- second symptom:

 Xlib: unexpected async reply (sequence 0x3a9e)!
 Xlib: sequence lost (0x19cc0  0x9cc1) in reply type 0xa!
 Connection lost to X server `:0.0'
 zsh: exit 70./emacs

and Emacs terminates immediately.

- third symptom: the selection dialogue opens, but hangs shortly after
  that; this can be when I use the C-l command, or when I accept the
  chose file; the dialogue window does not close, and the Emacs window
  displays a rotating circle; in the xterm calling Emacs there is the
  following message:

 Xlib: unexpected async reply (sequence 0xd2c1)!

How should I provide more information?

-- 


Olivier Lecarme


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


Re: [Patch] build cvs emacs for x86_64-sun-solaris10

2006-12-08 Thread Richard Stallman
--- src/fns.c   24 Nov 2006 19:53:56 -  1.422
+++ src/fns.c   8 Dec 2006 04:14:20 -
@@ -89,6 +89,8 @@
 #ifndef HAVE_UNISTD_H
 extern long time ();
 #endif
+
+static Lisp_Object concat (int, Lisp_Object *, enum Lisp_Type, int);
 

The need for that change is surprising, because fns.c already has a
prototype for `concat', before the first appearance of `concat'.
It shouldn't be necessary to have a second prototype.

What error happens without it?


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


Re: bad copyright years

2006-12-08 Thread Richard Stallman
There's not a single change that has been done in config.bat in the
years 2003 and 2005.  maintain.texi says (in node Copyright
Notices):

   To update the list of year numbers, add each year in which you have
made nontrivial changes to the package.

The package is GNU Emacs.  There have been changes in GNU Emacs every year.

We used to have a different practice, which you probably remember.
We changed it this year based on Eben Moglen's advice.


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


Re: no way to stop helpful modeline color tinkering

2006-12-08 Thread Richard Stallman
It looks like you just happened to use a background that looks very
much like a color by default used in the face `mode-line-inactive'.
You need to customize that face too, for good results.

So I think there is no bug here.


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