Re: calendar autoloads

2006-05-12 Thread Glenn Morris

Committed, thanks.



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


show-ifdef-block does not work when hide-ifdef-lines is t

2006-05-12 Thread Klaus Zeitler
1. load a C file with an ifdef block
2. turn on hide-ifdef-mode
3. hide-ifdef-block and show-ifdef-block work fine
4. set hide-ifdef-lines to t
5. hide-ifdef-block works, but show-ifdef-block only brings back one line
   of this block each time it is called


In GNU Emacs 22.0.50.12 (sparc-sun-solaris2.8, Motif Version 2.1.0)
 of 2006-05-12 on sfsws4
X server distributor `Sun Microsystems, Inc.', version 11.0.6410
configured using `configure '--with-gcc' 
'--prefix=/vol/freeware/SunOS-5.8/emacs/cvs' 
'--sharedstatedir=/vol/freeware/SunOS-5.8/emacs/cvs/share' 
'--with-x-toolkit=motif' 
'--x-includes=/usr/openwin/include:/usr/local/gnu/include:/opt/exp/gnu/include:/opt/exp/include:/opt/exp/lib/xpm/include'
 
'--x-libraries=/usr/openwin/lib:/usr/local/gnu/lib:/opt/exp/gnu/lib:/opt/exp/lib:/opt/exp/lib/xpm/lib'
 '--with-pop' 'CC=gcc''

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: C
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Major mode: C/l

Minor modes in effect:
  hide-ifdef-mode: t
  tooltip-mode: t
  auto-compression-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  line-number-mode: t
  abbrev-mode: t

Recent input:
. c return escape x h i d e i f SPC backspace 
backspace SPC i SPC SPC return down-mouse-1 mouse-movement 
mouse-1 escape x help-echo down-mouse-2 mouse-2 
return help-echo escape x up right right 
right right right left backspace backspace 
backspace backspace s h o w return M-: help-echo 
down-mouse-2 mouse-2 help-echo left left 
left right backspace backspace backspace 
help-echo backspace backspace right right 
return escape x up up return escape x up 
up return escape x up return escape x up 
return right right left escape x up return 
up down left left help-echo help-echo help-echo 
menu-bar help-menu report-emacs-bug

Recent messages:
(/usr/local/gnu/cvs/head/bin/emacs -Q)
For information about the GNU Project and its goals, type C-h C-p.
Loading cc-mode...done
Loading hideif...done
Hide-Ifdef mode enabled
t
Loading emacsbug...done


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


Sporadic segmentation faults

2006-05-12 Thread Klaus Zeitler
Since yesterday I had 4 crashes. All of them looked alike.
Here's a backtrace:

#0  0xfeb9feb4 in _libc_kill () from /usr/lib/libc.so.1
#1  0x000e452c in fatal_error_signal (sig=11) at 
/vol/freeware/cvs/emacs/head/emacs/src/emacs.c:430
#2  signal handler called
#3  0x000c0cc8 in handle_one_xevent (dpyinfo=0x489e00, eventp=0xffbebb90, 
finish=0xffbebb5c, hold_quit=0xffbecc98) at 
/vol/freeware/cvs/emacs/head/emacs/src/xterm.c:6086
#4  0x000c2298 in XTread_socket (sd=0, expected=1, hold_quit=0xffbecc98) at 
/vol/freeware/cvs/emacs/head/emacs/src/xterm.c:7034
#5  0x000ef7d4 in read_avail_input (expected=1) at 
/vol/freeware/cvs/emacs/head/emacs/src/keyboard.c:6716
#6  0x000efa04 in handle_async_input () at 
/vol/freeware/cvs/emacs/head/emacs/src/keyboard.c:6862
#7  0x000efa44 in input_available_signal (signo=22) at 
/vol/freeware/cvs/emacs/head/emacs/src/keyboard.c:6904
#8  signal handler called
#9  0xfeb9d8cc in _poll () from /usr/lib/libc.so.1
#10 0xfeb4d548 in select () from /usr/lib/libc.so.1
#11 0x001822e8 in wait_reading_process_output (time_limit=3, microsecs=0, 
read_kbd=1, do_display=1, wait_for_cell=3459073, wait_proc=0x0, 
just_wait_proc=0) at /vol/freeware/cvs/emacs/head/emacs/src/process.c:4502
#12 0x000504f0 in sit_for (sec=3, usec=0, reading=0, display=1, 
initial_display=1) at /vol/freeware/cvs/emacs/head/emacs/src/dispnew.c:6421
#13 0x0014ffd0 in Ffuncall (nargs=1, args=0xffbed628) at 
/vol/freeware/cvs/emacs/head/emacs/src/eval.c:2908
#14 0x0017b3c8 in Fbyte_code (bytestr=-4270552, vector=17801992, maxdepth=16) 
at /vol/freeware/cvs/emacs/head/emacs/src/bytecode.c:694
#15 0x00150360 in funcall_lambda (fun=17566724, nargs=0, arg_vector=0xffbed7c4) 
at /vol/freeware/cvs/emacs/head/emacs/src/eval.c:3089
#16 0x0014fe64 in Ffuncall (nargs=0, args=0xffbed7c0) at 
/vol/freeware/cvs/emacs/head/emacs/src/eval.c:2957
#17 0x0017b3c8 in Fbyte_code (bytestr=-4270144, vector=17801736, maxdepth=32) 
at /vol/freeware/cvs/emacs/head/emacs/src/bytecode.c:694
#18 0x00150360 in funcall_lambda (fun=17565924, nargs=0, arg_vector=0xffbeda08) 
at /vol/freeware/cvs/emacs/head/emacs/src/eval.c:3089
#19 0x0014fe64 in Ffuncall (nargs=0, args=0xffbeda04) at 
/vol/freeware/cvs/emacs/head/emacs/src/eval.c:2957
#20 0x0014f994 in run_hook_with_args (nargs=1, args=0xffbeda04, 
cond=to_completion) at /vol/freeware/cvs/emacs/head/emacs/src/eval.c:2565
#21 0x0014f858 in Frun_hooks (nargs=1, args=0xffbedb0c) at 
/vol/freeware/cvs/emacs/head/emacs/src/eval.c:2428
#22 0x0014ffb4 in Ffuncall (nargs=1, args=0xffbedb08) at 
/vol/freeware/cvs/emacs/head/emacs/src/eval.c:2905
#23 0x0014fbc4 in call1 (fn=3555193, arg1=3508321) at 
/vol/freeware/cvs/emacs/head/emacs/src/eval.c:2687
#24 0x0014e1c0 in internal_condition_case (bfun=0xe8fdc safe_run_hooks_1, 
handlers=3459121, hfun=0xe8ff8 safe_run_hooks_error) at 
/vol/freeware/cvs/emacs/head/emacs/src/eval.c:1474
#25 0x000e9084 in safe_run_hooks (hook=3459121) at 
/vol/freeware/cvs/emacs/head/emacs/src/keyboard.c:2064
#26 0x000e7858 in command_loop_1 () at 
/vol/freeware/cvs/emacs/head/emacs/src/keyboard.c:1810
#27 0x0014e1c0 in internal_condition_case (bfun=0xe73d8 command_loop_1, 
handlers=3523185, hfun=0xe6e24 cmd_error) at 
/vol/freeware/cvs/emacs/head/emacs/src/eval.c:1474
#28 0x000e71a8 in command_loop_2 () at 
/vol/freeware/cvs/emacs/head/emacs/src/keyboard.c:1328
#29 0x0014dc6c in internal_catch (tag=3517441, func=0xe7184 command_loop_2, 
arg=3459073) at /vol/freeware/cvs/emacs/head/emacs/src/eval.c:1212
#30 0x000e7134 in command_loop () at 
/vol/freeware/cvs/emacs/head/emacs/src/keyboard.c:1307
#31 0x000e6b68 in recursive_edit_1 () at 
/vol/freeware/cvs/emacs/head/emacs/src/keyboard.c:1000
#32 0x000e6cc4 in Frecursive_edit () at 
/vol/freeware/cvs/emacs/head/emacs/src/keyboard.c:1061
#33 0x000e5a30 in main (argc=0, argv=0xffbee264) at 
/vol/freeware/cvs/emacs/head/emacs/src/emacs.c:1789



In GNU Emacs 22.0.50.12 (sparc-sun-solaris2.8, Motif Version 2.1.0)
 of 2006-05-12 on sfsws4
X server distributor `Sun Microsystems, Inc.', version 11.0.6410
configured using `configure '--with-gcc' 
'--prefix=/vol/freeware/SunOS-5.8/emacs/cvs' 
'--sharedstatedir=/vol/freeware/SunOS-5.8/emacs/cvs/share' 
'--with-x-toolkit=motif' 
'--x-includes=/usr/openwin/include:/usr/local/gnu/include:/opt/exp/gnu/include:/opt/exp/include:/opt/exp/lib/xpm/include'
 
'--x-libraries=/usr/openwin/lib:/usr/local/gnu/lib:/opt/exp/gnu/lib:/opt/exp/lib:/opt/exp/lib/xpm/lib'
 '--with-pop' 'CC=gcc''

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: C
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  auto-compression-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  

Re: Sporadic segmentation faults

2006-05-12 Thread Jan Djärv



Klaus Zeitler skrev:

Since yesterday I had 4 crashes. All of them looked alike. Here's a
backtrace:

#0  0xfeb9feb4 in _libc_kill () from /usr/lib/libc.so.1 #1  0x000e452c in
fatal_error_signal (sig=11) at
/vol/freeware/cvs/emacs/head/emacs/src/emacs.c:430 #2  signal handler
called #3  0x000c0cc8 in handle_one_xevent (dpyinfo=0x489e00,
eventp=0xffbebb90, finish=0xffbebb5c, hold_quit=0xffbecc98) at
/vol/freeware/cvs/emacs/head/emacs/src/xterm.c:6086


f is dereferenced at this line before it is checked to be != 0.  It is related 
to this change:


2006-03-24  Kim F. Storm  [EMAIL PROTECTED]

* xterm.c (handle_one_xevent):
* w32term.c (w32_read_socket):
* macterm.c (XTread_socket): Don't let key-press clear mouse face
on in toolbar window if mouse-highlight is an integer.


I am not sure what the correct fix is.

Jan D.


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


with-temp-buffer and undo [was: Big desktop undo buffer crashes Emacs]

2006-05-12 Thread Lars Hansen
Lars Hansen wrote:

I suggest to use with-temp-buffer (and buffer-disable-undo)
  

Does it ever make sense to save undo information in a temporary buffer?
If not, I suggest to disable it in with-temp-buffer.
Patch attached.
*** subr.el~	2006-05-12 08:24:10.0 +0200
--- subr.el	2006-05-12 12:40:59.575290323 +0200
***
*** 2220,2226 
  See also `with-temp-file' and `with-output-to-string'.
(declare (indent 0) (debug t))
(let ((temp-buffer (make-symbol temp-buffer)))
! `(let ((,temp-buffer (generate-new-buffer  *temp*)))
 (unwind-protect
  	   (with-current-buffer ,temp-buffer
  	 ,@body)
--- 2220,2227 
  See also `with-temp-file' and `with-output-to-string'.
(declare (indent 0) (debug t))
(let ((temp-buffer (make-symbol temp-buffer)))
! `(let ((,temp-buffer (generate-new-buffer  *temp*))
!(buffer-undo-list t))
 (unwind-protect
  	   (with-current-buffer ,temp-buffer
  	 ,@body)
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: with-temp-buffer and undo [was: Big desktop undo buffer crashes Emacs]

2006-05-12 Thread Eli Zaretskii
 Date: Fri, 12 May 2006 12:50:23 +0200
 From: Lars Hansen [EMAIL PROTECTED]
 Cc: emacs-pretest-bug@gnu.org, Luc Teirlinck [EMAIL PROTECTED],
   [EMAIL PROTECTED], [EMAIL PROTECTED]
 
 Does it ever make sense to save undo information in a temporary buffer?

Why not?  The fact that it's temporary doesn't necessarily mean it
cannot be used interactively.  For example, I could imagine some
specialized mode that pops up a temporary buffer where the user is
supposed to type some text that the mode then uses.  Some VC-related
feature could, for example, ask for a comment or descriptive text that
way.



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


Re: with-temp-buffer and undo [was: Big desktop undo buffer crashes Emacs]

2006-05-12 Thread Andreas Schwab
Lars Hansen [EMAIL PROTECTED] writes:

 Lars Hansen wrote:

I suggest to use with-temp-buffer (and buffer-disable-undo)
  

 Does it ever make sense to save undo information in a temporary buffer?
 If not, I suggest to disable it in with-temp-buffer.
 Patch attached.
 *** subr.el~  2006-05-12 08:24:10.0 +0200
 --- subr.el   2006-05-12 12:40:59.575290323 +0200
 ***
 *** 2220,2226 
   See also `with-temp-file' and `with-output-to-string'.
 (declare (indent 0) (debug t))
 (let ((temp-buffer (make-symbol temp-buffer)))
 ! `(let ((,temp-buffer (generate-new-buffer  *temp*)))
  (unwind-protect
  (with-current-buffer ,temp-buffer
,@body)
 --- 2220,2227 
   See also `with-temp-file' and `with-output-to-string'.
 (declare (indent 0) (debug t))
 (let ((temp-buffer (make-symbol temp-buffer)))
 ! `(let ((,temp-buffer (generate-new-buffer  *temp*))
 !(buffer-undo-list t))
  (unwind-protect
  (with-current-buffer ,temp-buffer
,@body)

This won't disable undo in the temp buffer, you'd need to move that below
with-current-buffer.

Andreas.

-- 
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
And now for something completely different.


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


Re: with-temp-buffer and undo [was: Big desktop undo buffer crashes Emacs]

2006-05-12 Thread Lars Hansen
Andreas Schwab wrote:

This won't disable undo in the temp buffer, you'd need to move that below
with-current-buffer.
  

Oops.


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


Re: Big desktop undo buffer crashes Emacs

2006-05-12 Thread Stefan Monnier
 !   (when (consp buffer-undo-list)
 !(setq buffer-undo-list nil))
 !   (let ((buffer-undo-list t))
 !(erase-buffer)

Why not just (buffer-disable-undo) ??

 Because I want to allow people who visit the buffer to undo any
 changes they deliberately or inadvertently make to it.

That's what I understood, but why?
Actually, a better question is: why is it called *desktop* rather
than  *desktop*?
Calling it  *desktop* would not just hide the buffer but would also
disable undo.  It's an internal buffer, after all, that normal users aren't
supposed to display or edit.


Stefan


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


Re: with-temp-buffer and undo

2006-05-12 Thread Stefan Monnier
 ! `(let ((,temp-buffer (generate-new-buffer  *temp*))
 !(buffer-undo-list t))

Buffer whose name start with a space have their undo disabled by default.
I.e. someone thought of that years ago already,


Stefan


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


Re: add info about safe-local-variable to describe-variable

2006-05-12 Thread Ken Manheimer

On 5/11/06, Richard Stallman [EMAIL PROTECTED] wrote:

 But there are also expressions in `allout.el' where no predefined
 predicate exists (AFAICS):

 allout-use-mode-specific-leader
 allout-reindent-bodies
 allout-layout

is it necessary to have a predefined predicate in all cases, or will
quoting the lambda be sufficient?

Quoting the lambda is sufficient.


i've attached a patch (allout-patch.txt), ChangeLog
(allout-ChangeLog.txt), and revised NEWS fragment (allout-NEWS.txt)
for allout that addresses the stuff we've been discussing, and a few
other things.

in the patch, any autoloaded safe-local-variables lambdas are quoted.
the patch also incorporates some of the other refinements that were
suggested in this discussion, though i am leaving the
safe-local-variable property assignments as active code (rather than
containing them in the autoload comment) and continuing to use a
lambda rather than booleanp.  both of these measures will make it
easier to use allout in older emacs, without adding significant
complexity.

the patch also includes a few small fixes, including the start on
deprecating a poorly named hook variable.  that last is the reason
thatm i'm including a new version of the fragment for the NEWS file,
which describes the deprecation and fixes a typo or two in the old
NEWS fragment.

the complete set of changes from the currently checked-in allout
version is described in the attached ChangeLog.

--
ken
[EMAIL PROTECTED]
http://myriadicity.net
2006-05-11  Ken Manheimer  [EMAIL PROTECTED]

* allout.el: (allout-view-change-hook): Marked as being deprecated,
to be replaced by `allout-exposure-change-hook'.
(allout-exposure-change-hook): New, replacing
`allout-view-change-hook'.
(allout-flag-region): Run new hook `allout-exposure-change-hook',
in addition to `allout-view-change-hook'.
(allout-show-bodies, allout-old-style-prefixes)
(allout-stylish-prefixes, allout-use-hanging-indents): Quote the
lambda forms to prevent their showing up in variable help
presentations as inscrutable byte-compiled code.
(allout-numbered-bullet, allout-file-xref-bullet, allout-layout):
Use string-or-null-p to qualify safe-local-variable values.
(allout-reindent-bodies): Use memq to qualify matches against
valid safe-local-variable values.  Also, quote the lambda as above.
(allout-use-mode-specific-leader): Add missing candidate-value
symbols, use memq, and quote the lambda.
(allout-overlay-interior-modification-handler): Remove unused
variables `msg' and 'opened'.
(allout-hidden-p): Constrain invisibility consideration to allout's
invisibility spec, disregarding invisibility for other reasons.


** Changes in Allout

*** Topic cryptography added, enabling easy gpg topic encryption and
decryption.  Per-topic basis enables interspersing encrypted-text and
clear-text within a single file to your heart's content, using symmetric
and/or public key modes.  Time-limited key caching, user-provided
symmetric key hinting and consistency verification, auto-encryption of
pending topics on save, and more, make it easy to use encryption in
powerful ways.

*** `allout-view-change-hook' marked as being deprecated - use
`allout-exposure-change-hook' instead.  Both are currently being used, but
`allout-view-change-hook' will be ignored in a subsequent allout version.

*** Default command prefix changed to \C-c  (control-c space), to avoid
intruding on user's keybinding space.  Customize the
`allout-command-prefix' variable to your preference.

*** Allout now uses text overlay's `invisible' property (and others) for
concealed text, instead of selective-display.  This simplifies the code, in
particular avoiding the need for kludges for isearch dynamic-display,
discretionary handling of edits of concealed text, undo concerns, etc.

*** Many substantial fixes and refinements, including:

   - repaired inhibition of inadvertent edits to concealed text
   - repaired retention of topic body hanging indent upon topic depth shifts
   - refuse to create containment discontinuities, where a
 topic is shifted deeper than the offspring-depth of its' container
   - bulleting variation is simpler and more accommodating, both in the
 default behavior and in ability to vary when creating new topics
   - many internal fixes and refinements
   - many module and function docstring clarifications
   - version number incremented to 2.2


Index: allout.el
===
RCS file: /sources/emacs/emacs/lisp/allout.el,v
retrieving revision 1.74
diff -u -u -r1.74 allout.el
--- allout.el   28 Apr 2006 05:09:13 -  1.74
+++ allout.el   12 May 2006 14:46:26 -
@@ -199,7 +199,7 @@
 (make-variable-buffer-local 'allout-show-bodies)
 ;;;###autoload
 (put 'allout-show-bodies 'safe-local-variable
- 

Re: add info about safe-local-variable to describe-variable

2006-05-12 Thread Reiner Steib
On Fri, May 12 2006, Richard Stallman wrote:

 Maybe it would be better to shift it down so that it comes _after_ the
 documentation:

 No, because the documentation is much longer than the safe-values
 info.  if you put a small thing after a big thing, people tend not no
 notice the small thing.

In general, I agree to this.  But in this case, IMHO it would make
sense to have it below, because without reading the documentation
which should explain the meaning of the various allowed values,
printing the safe-value information often is not very useful.

Bye, Reiner.
-- 
   ,,,
  (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/


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


Re: add info about safe-local-variable to describe-variable

2006-05-12 Thread Reiner Steib
On Fri, May 12 2006, Ken Manheimer wrote:

 i've attached a patch (allout-patch.txt), ChangeLog
 (allout-ChangeLog.txt), and revised NEWS fragment (allout-NEWS.txt)
 for allout that addresses the stuff we've been discussing, and a few
 other things.

Thanks, I have committed your changes.

 in the patch, any autoloaded safe-local-variables lambdas are quoted.
 the patch also incorporates some of the other refinements that were
 suggested in this discussion, though i am leaving the
 safe-local-variable property assignments as active code (rather than
 containing them in the autoload comment) 

A drawback is that user's won't see the predicate in the output of
`describe-variable':

,
| This variable is safe as a file local variable if its value
| satisfies the predicate which is byte-compiled expression.
`

 and continuing to use a lambda rather than booleanp.  both of these
 measures will make it easier to use allout in older emacs, without
 adding significant complexity.

But here, I still don't think it makes much sense to provide backward
compatibility for older CVS Emacs versions.  Not using `booleanp'
makes the code and the output of `describe-variable' harder to read.

If you can't update your CVS Emacs, you could define `booleanp' if
it's not bound.

Bye, Reiner.
-- 
   ,,,
  (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/


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


Re: add info about safe-local-variable to describe-variable

2006-05-12 Thread Ken Manheimer

On 5/12/06, Reiner Steib [EMAIL PROTECTED] wrote:

On Fri, May 12 2006, Ken Manheimer wrote:

 i've attached a patch (allout-patch.txt), ChangeLog
 (allout-ChangeLog.txt), and revised NEWS fragment (allout-NEWS.txt)
 for allout that addresses the stuff we've been discussing, and a few
 other things.

Thanks, I have committed your changes.


thanks!


 in the patch, any autoloaded safe-local-variables lambdas are quoted.
 the patch also incorporates some of the other refinements that were
 suggested in this discussion, though i am leaving the
 safe-local-variable property assignments as active code (rather than
 containing them in the autoload comment)

A drawback is that user's won't see the predicate in the output of
`describe-variable':

,
| This variable is safe as a file local variable if its value
| satisfies the predicate which is byte-compiled expression.
`


the lambdas are quoted, so they ought to show as text.  (they do for me.)


 and continuing to use a lambda rather than booleanp.  both of these
 measures will make it easier to use allout in older emacs, without
 adding significant complexity.

But here, I still don't think it makes much sense to provide backward
compatibility for older CVS Emacs versions.  Not using `booleanp'
makes the code and the output of `describe-variable' harder to read.


i don't understand.  older emacs 22 CVS versions are not my concern -
emacs 21 and earlier lack booleanp.


If you can't update your CVS Emacs, you could define `booleanp' if
it's not bound.


i debated providing a booleanp definition if not already fboundp, but
considered that more clutter than just using the lambda.  i can be
convinced otherwise, but it seems like a fairly close call, one way or
the other.
--
ken manheimer
[EMAIL PROTECTED]
http://myriadicity.net


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


Re: with-temp-buffer and undo

2006-05-12 Thread Lars Hansen
Stefan Monnier wrote:

! `(let ((,temp-buffer (generate-new-buffer  *temp*))
!(buffer-undo-list t))



Buffer whose name start with a space have their undo disabled by default.
I.e. someone thought of that years ago already,
  

Cool :-)


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


Re: with-temp-buffer and undo

2006-05-12 Thread Lars Hansen
Stefan Monnier wrote:

! `(let ((,temp-buffer (generate-new-buffer  *temp*))
!(buffer-undo-list t))



Buffer whose name start with a space have their undo disabled by default.
I.e. someone thought of that years ago already,
  

Then my previous patch can be simplified.
Any objections?
*** desktop.el.~1.99.~	2006-02-19 15:43:52.0 +0100
--- desktop.el	2006-05-12 19:42:09.642918747 +0200
***
*** 763,773 
  (setq locals (cdr locals)))
ll)))
(buffer-list)))
!   (eager desktop-restore-eager)
!   (buf (get-buffer-create *desktop*)))
!   (set-buffer buf)
!   (erase-buffer)
! 
(insert
  ;; -*- mode: emacs-lisp; coding: emacs-mule; -*-\n
  desktop-header
--- 763,770 
  (setq locals (cdr locals)))
ll)))
(buffer-list)))
!   (eager desktop-restore-eager))
!   (with-temp-buffer
  (insert
   ;; -*- mode: emacs-lisp; coding: emacs-mule; -*-\n
   desktop-header
***
*** 801,807 
  info)
(setq default-directory dirname)
(let ((coding-system-for-write 'emacs-mule))
! (write-region (point-min) (point-max) filename nil 'nomessage
(setq desktop-dirname dirname))
  
  ;; 
--- 798,804 
info)
  (setq default-directory dirname)
  (let ((coding-system-for-write 'emacs-mule))
!   (write-region (point-min) (point-max) filename nil 'nomessage)
(setq desktop-dirname dirname))
  
  ;; 
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug


Re: with-temp-buffer and undo

2006-05-12 Thread Bill Wohler
Lars Hansen [EMAIL PROTECTED] wrote:

 Stefan Monnier wrote:
 
 ! `(let ((,temp-buffer (generate-new-buffer  *temp*))
 !(buffer-undo-list t))
 
 
 
 Buffer whose name start with a space have their undo disabled by default.
 I.e. someone thought of that years ago already,
   
 
 Then my previous patch can be simplified.
 Any objections?

None from me. I've applied it and will let you know how it goes. Thanks.

-- 
Bill Wohler [EMAIL PROTECTED]  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.


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


C-h f fringe-mode shows Not documented

2006-05-12 Thread Drew Adams
emacs -Q

C-h f fringe-mode shows only this:

 fringe-mode is an interactive compiled Lisp function in `fringe.el'.
 (fringe-mode optional mode)

 Not documented.

Even after calling `fringe-mode' I get the same thing. I must load the
source file (.el, not .elc) in order to be able to see the doc of
`fringe-mode'.


In GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600)
 of 2006-03-20 on W2ONE
X server distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --cflags -Id:/g/include'

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

Major mode: Dired by name

Minor modes in effect:
  encoded-kbd-mode: t
  tooltip-mode: t
  auto-compression-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  line-number-mode: t

Recent input:
help-echo down-mouse-1 mouse-1 M-x f r i n C-g
C-g C-h f f r i n g e - m o d e return M-x f r i
n g e - m o d e return C-g C-h f M-p return M-x
f r i n g e - m o d e return n i backspace o n
e return C-h f M-p return M-p return help-echo
help-echo help-echo help-echo help-echo menu-bar
help-menu report-emacs-bug

Recent messages:
Loading encoded-kb...done
For information about the GNU Project and its goals, type C-h C-p.
Loading dired...
Loading regexp-opt...done
Loading dired...done
Quit [2 times]
Loading help-fns...done
Type C-x 1 to remove help window.
Quit
Loading emacsbug...done



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


several extra pixels between text and scroll bar

2006-05-12 Thread Drew Adams
emacs -Q

M-x fringe-mode none

I see, systematically, about 3 or 4 extra pixels (background) just to
the left of the scroll bar (which is on the right). No matter how I
resize the frame, the rightmost character visible on a display line is
never right up against the scroll bar (whereas the leftmost character
is right up against the frame border).

If I turn off scroll-bar-mode, then the problem goes away (rightmost
char is up against frame border). It seems that there is extra
horizontal space to the left of the scroll bar.


In GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600)
 of 2006-03-20 on W2ONE
X server distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --cflags -Id:/g/include'

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

Major mode: Info

Minor modes in effect:
  encoded-kbd-mode: t
  tooltip-mode: t
  auto-compression-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  line-number-mode: t

Recent input:
mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 mouse-1 help-echo 
down-mouse-2 mouse-2 u help-echo help-echo 
help-echo help-echo help-echo wheel-up double-wheel-up 
triple-wheel-up triple-wheel-down wheel-up help-echo 
help-echo help-echo down-mouse-2 mouse-2 C-x 
1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 
mouse-1 mouse-1 mouse-1 down-mouse-1 mouse-1 
help-echo help-echo help-echo help-echo help-echo 
help-echo help-echo help-echo menu-bar help-menu 
report-emacs-bug

Recent messages:
Auto-saving...done
Mark set
Sending...
Loading mailclient...done
Loading browse-url...done
Sending...done
Loading info...
Loading easymenu...done
Loading info...done
Composing main Info directory...done



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


Re: with-temp-buffer and undo [was: Big desktop undo buffer crashes Emacs]

2006-05-12 Thread Richard Stallman
Using with-temp-buffer seems like a good idea.

Does it ever make sense to save undo information in a temporary buffer?
If not, I suggest to disable it in with-temp-buffer.

Undo is always disabled for with-temp-buffer, because it is disabled
by default for buffers whose names start with space.



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


Re: add info about safe-local-variable to describe-variable

2006-05-12 Thread Richard Stallman
In general, I agree to this.  But in this case, IMHO it would make
sense to have it below, because without reading the documentation
which should explain the meaning of the various allowed values,
printing the safe-value information often is not very useful.

You can read them in either order.


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


Re: with-temp-buffer and undo

2006-05-12 Thread Richard Stallman
Then my previous patch can be simplified.
Any objections?

Your patch looks good to me.


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