tcl.el

I made the following change to tcl.el in order to make it format
paragraphs (fill-paragraph) correctly in comments.  I sent email about
the same problem earlier, but never heard anything back... although it
was during your outage.

--- /usr/share/emacs/21.2/lisp/progmodes/tcl.el Fri Mar 22 09:03:00 2002
+++ /home/davidw/.elisp/tcl.el  Wed Oct 30 18:53:52 2002
 <at>  <at>  -1542,14 +1542,14  <at>  <at> 
               p-start p-end)
           ;; Search backwards.
           (save-excursion
-            (while (looking-at "^[ \t]*#")
+            (while (looking-at "^[ \t]*#\\s-*$")
               (forward-line -1))
             (forward-line)
             (setq p-start (point)))

           ;; Search forwards.
           (save-excursion
-            (while (looking-at "^[ \t]*#")
+            (while (looking-at "^[ \t]*#\\s-*$")
               (forward-line))
             (setq p-end (point)))

Thankyou for your time and attention,
--

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
     Personal: http://www.dedasys.com/davidw/

Re: ispell/aspell misalignment

Have you sent an Aspell bug report for the new bug?
If not, would you please do that?  The maintainer
can't fix it if he doesn't know about it.

[gnu.org #5318] Benjamin E Key

Since I plan to continue to contribute to GNU Emacs, I would prefer to sign
an assignment of past and future
changes rather than simply signing an assignment for my current change.

Re: they never thought I would query-replace an uppercase

>>>>> "RMS" == Richard Stallman <rms <at> gnu.org> writes:

RMS> Do you think this is clear?
RMS> Matching is independent of case if `case-fold-search' is non-nil and
RMS> REGEXP has no uppercase letters.  Replacement transfers the case
RMS> pattern of the old text to the new text, if `case-replace' and
RMS> `case-fold-search' are non-nil and REGEXP has no uppercase letters.
RMS> \(Transferring the case pattern means that if the old text matched is
RMS> all caps, or capitalized, then its replacement is upcased or
RMS> capitalized.)

Perhaps.  However I pack a Limited Edition brain, so am not sure.
Another approach would be to just describe each affecting variable.
OK, over and out on this subject.
--

-- 
http://jidanni.org/ Taiwan(04)25854780

Infinite recursion: Customize Faces/Basic faces/Default/Height

I'm using GNU Emacs 21.2.1 from Debian 3 r0.

If I customize Faces/Basic faces/Default, adjusting Height (in 1/10
point units) to 140, and then apply the change to the current session,
emacs appears to go into an infinite loop.  The only frame present
clears of all text, and repeatedly resizes between maximised and a
smaller size, until I kill it.

Using scale rather than point size causes the same problem.  Other
options in the group do not cause a problem.

If I change another option in the group, then look in .emacs to see
what customize generated, I find this:

(custom-set-faces
  ;; custom-set-faces was added by Custom -- don't edit or cut/paste it!
  ;; Your init file should contain only one such instance.
 '(default ((t (:stipple nil :background "#ffffff" :foreground "#000000"
 :inverse-video nil :box nil :strike-through nil :overline nil :underline
 nil :slant normal :weight normal :height 164 :width condensed :family
 "adobe-courier")))))

This works fine.  If I then manually change height to 140, emacs has
trouble at
startup:

> (/usr/bin/emacs)
> Loading disp-table...done
> Loading tool-bar...done
> Loading image...done

Russian keyboard input method

Hi,

The most common keyboard for PC is so called microsoft compatiable keyboard.
I added russian keyboard layout for this keyboard to attached file.

-- 
Olleg Samoylov

;;; quail/cyrillic.el -- Quail package for inputting Cyrillic characters

;; Copyright (C) 1997 Electrotechnical Laboratory, JAPAN.
;; Licensed to the Free Software Foundation.

;; Keywords: multilingual, input method, Cyrillic

;; This file is part of GNU Emacs.

;; GNU Emacs is free software; you can redistribute it and/or modify
;; it under the terms of the GNU General Public License as published by
;; the Free Software Foundation; either version 2, or (at your option)
;; any later version.

;; GNU Emacs is distributed in the hope that it will be useful,
;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
;; GNU General Public License for more details.

;; You should have received a copy of the GNU General Public License
;; along with GNU Emacs; see the file COPYING.  If not, write to the

Problems with custom configuration file (.gnu-emacs-custom)

This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the bug-gnu-emacs <at> gnu.org mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.2.1 (i586-suse-linux, X toolkit, Xaw3d scroll bars)
 of 2002-09-11 on amdsimb
configured using `configure '--with-gcc' '--with-pop' '--with-system-malloc' '--prefix=/usr'
'--exec-prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man'
'--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--with-x' '--with-xpm' '--with-jpeg'
'--with-tiff' '--with-gif' '--with-png' '--with-x-toolkit=lucid'
'--x-includes=/usr/X11R6/include' '--x-libraries=/usr/X11R6/lib' 'i586-suse-linux' 'CC=gcc'
'CFLAGS=-O2 -march=i586 -mcpu=i686 -fmessage-length=0 -pipe 	 -DSYSTEM_PURESIZE_EXTRA=25000 	
-DSITELOAD_PURESIZE_EXTRA=10000 	 -D_GNU_SOURCE ' 'LDFLAGS=-s' 'build_alias=i586-suse-linux'
'host_alias=i586-suse-linux' 'target_alias=i586-suse-linux''
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: POSIX
  value of $LC_CTYPE: ru_RU.KOI8-R
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US
  locale-coding-system: cyrillic-koi8
  default-enable-multibyte-characters: t

RMAIL should ask for confirmation before sending mail

Recently RMAIL started asking for confirmation before deleting marked
messages.  I appreciate this, having occasionally deleted messages
prematurely in the past.

I propose that mail-send-and-exit also ask for confirmation.  Several
times, I have accidentally sent mail before I had finished editing it.
This can be embarrassing, especially when there are a lot of
addressees.  I believe that makes mail-send-and-exit a "dangerous"
command. 

I may make the mistake because mail-send-and-exit is bound to C-c C-c,
which in the related RMAIL edit mode runs the comparatively safe
command rmail-cease-edit.  I think in general one should avoid binding
safe and dangerous commands to the same key, at least in related edit
modes.  On the other hand, my fingers have learned C-c C-c as the way
to finish both modes.  Asking for confirmation seems the appropriate
extra measure of protection for the dangerous command.

		- Jim Van Zandt

Re: RMAIL should ask for confirmation before sending mail

On Mon, 4 Nov 2002 08:39:12 -0500 (EST), Jim Van Zandt <jrv <at> kosh.mitre.org> wrote:
> 
> I propose that mail-send-and-exit also ask for confirmation.  Several
> times, I have accidentally sent mail before I had finished editing it.
> This can be embarrassing, especially when there are a lot of
> addressees.  I believe that makes mail-send-and-exit a "dangerous"
> command. 

I have defined 2 functions to do this (plus renaming the *mail* buffer)
and it helped me a few times.

(defun mail-send-rename ( )
  "Don't send by accident, rename mail buffer to some sensible value"
       (interactive)
       (and (yes-or-no-p "Do you really want to send this mail")
           (let ((subj "(No Subject)"))
               (save-excursion
                   (goto-char (point-min))
                   (and (re-search-forward "^[Ss]ubject: " nil t)
                        (setq subj (buffer-substring (point) (line-end-position)))))
               (call-interactively 'mail-send)
               (rename-buffer (concat "*mail-" subj "-sent*") 'unique))))

(defun mail-send-rename-exit ( )
  "Bury buffer after sending"
       (interactive)
       (and (mail-send-rename)
            (bury-buffer)))

Now, assign the new functions to default keys:

wrong default for backup-by-copying-when-linked?

This can't be a new issue, but I don't recall discussion of it.  It
seems to me that backup-by-copying-when-linked should default to t, as
I actually thought it did.  I've just been bitten by breaking links to
some system configuration files.

Is there a good reason for the current default of nil?  If so, I think
it should at least be commented.