Feature wish: make smtpmail process buffer available
In GNU Emacs 22.1.50.1 (i686-pc-linux-gnu) of 2007-04-30 on brabbelbox Windowing system distributor `The X.Org Foundation', version 11.0.70101000 configured using `configure 'CC=gcc'' Hello, i wrote two defadvice wrappers for gnus. I want to switch to the process buffer, when `smtpmail-debug-info' is not nil. But the process buffer name template is hardcoded in "smtpmail.el". So i suggest to define and use a customizable variable, so that i can use safely something like (when smtpmail-debug-info (switch-to-buffer (format smtpmail-process-buffer-template smtpmail-smtp-server))) Best regards, Christoph ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Feature wish: make smtpmail process buffer available
In GNU Emacs 22.1.50.1 (i686-pc-linux-gnu) of 2007-04-30 on brabbelbox Windowing system distributor `The X.Org Foundation', version 11.0.70101000 configured using `configure 'CC=gcc'' Hello, i wrote two defadvice wrappers for gnus. I want to switch to the process buffer, when `smtpmail-debug-info' is not nil. But the process buffer name template is hardcoded in "smtpmail.el". So i suggest to define and use a customizable variable, so that i can use safely something like (when smtpmail-debug-info (switch-to-buffer (format smtpmail-process-buffer-template smtpmail-smtp-server))) Best regards, Christoph ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: python.el
Richard Stallman <[EMAIL PROTECTED]> writes: > > However, 1.40 (2006-08-20) by you is extensive and the changelog says > > "Update to Dave Love's latest version". Was this directly from him? > > We could simply revert to the pre-2006-08-20 version and reapply > subsequent tiny changes. Will satisfy everybody (including RMS)? > > I don't know yet. I need to get more info from Dave Love, and discuss > the matter with a lawyer, to find out whether his previous code is > really ok to use. In that case, why not remove Python support in Emacs 22.1? We can put it back for 22.2, if and when the legal issues get sorted out. Note that Emacs 21 did not have Python support, so this will not be a step backward in that sense. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Regexp not stateless?
> (defconst mumamo-script-tag-start-regex > (rx " (1+ space) > "type" > (0+ space) > "=" > (0+ space) > ?\" > ;;(or "text" "application") > ;;"/" > ;;(or "javascript" "ecmascript") > "text/javascript" > ?\" > (0+ (not (any ">"))) > ">" > (optional (0+ space) "
lispref paragraph break due to @anchor
In the current cvs, the "Signaling Errors" node of the elisp manual has
-- Function: signal error-symbol data
This
function signals an error named by ERROR-SYMBOL. The argument
DATA is a list of additional Lisp objects relevant to the
circumstances of the error.
which I think is an unintended paragraph break.
I think it's caused by @anchor on a line of its own in the source. I
get some joy from the change below, following the style shown in the
texinfo manual, ie. hanging it onto the start of a word.
2007-04-30 Kevin Ryde <[EMAIL PROTECTED]>
* control.texi (Signaling Errors): In `signal', join @anchor into
paragraph text, to avoid a paragraph break after the first
word "This".
*** control.texi 12 Mar 2007 10:17:08 +1100 1.31
--- control.texi 30 Apr 2007 10:53:48 +1000
***
*** 783,795
@end defun
@defun signal error-symbol data
- This
- @anchor{Definition of signal}
@c unfortunately, a page break is allowed if the anchor immediately
@c follows the @defun, due to hard-to-fix TeXnicalities.
! function signals an error named by @var{error-symbol}. The
! argument @var{data} is a list of additional Lisp objects relevant to the
! circumstances of the error.
The argument @var{error-symbol} must be an @dfn{error symbol}---a symbol
bearing a property @code{error-conditions} whose value is a list of
--- 783,793
@end defun
@defun signal error-symbol data
@c unfortunately, a page break is allowed if the anchor immediately
@c follows the @defun, due to hard-to-fix TeXnicalities.
! This @anchor{Definition of signal}function signals an error named by
! @var{error-symbol}. The argument @var{data} is a list of additional
! Lisp objects relevant to the circumstances of the error.
The argument @var{error-symbol} must be an @dfn{error symbol}---a symbol
bearing a property @code{error-conditions} whose value is a list of
In GNU Emacs 22.0.98.2 (i586-pc-linux-gnu, GTK+ Version 2.8.20)
of 2007-04-18 on blah
configured using `configure 'CFLAGS=-O' '--prefix=/down/emacs/b/inst'
'--with-x-toolkit=gtk''
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: en_AU
locale-coding-system: iso-8859-1
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: \s description in NEWS
> In strings, \s is always interpreted as a space. > The last sentence is not true; "\s-..." gives an "Invalid modifier" > error. > Since \s is mainly intended for character constants, rather than for > strings, I changed etc/NEWS. We should also consider it as a bug (to fix in Emacs-23 only, of course): since the super modifier \s-... is meaningless in a string, it should not signal an error but be interpreted as " -...". Stefan ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: eval-last-sexp narrows buffer on error
martin rudalics <[EMAIL PROTECTED]> writes: >> I've tried. From what I can tell `specpdl' isn't being wound back >> afterwards, so `save_restriction_restore' is never called. >> >> In fact, this apparently is the case after any error (unless caught by >> `condition-case'), so `specpdl' grows bigger and bigger. Is that >> supposed to happen?? >> >> The functions called by `error' are >> * signal >> ** find_handler_clause >> *** call_debuger > > I'm too silly. Try to run with `debug-on-error' and > `eval-expression-debug-on-error' both nil. Okay, the problem doesn't occur then. regards, Nikolaj Schumacher ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Rather a request for an enhancement, or two, in GNU Emacsen 22 and 23
I made this change. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: eval-last-sexp narrows buffer on error
It's a problem with `save-restriction'. Take: (with-current-buffer (get-buffer-create "*foo*") (delete-region (point-min) (point-max)) (insert "foo\nbar\nfoo\n") (save-restriction (narrow-to-region (line-beginning-position -1) (line-end-position -1)) (error ""))) It will leave the buffer narrowed although the doc-string of `save-restriction' says: It did not fail when I tried it. I tried it in two ways: using C-M-x, and by putting that code into the body of a function (defun foo () (interactive) (with-current-buffer (get-buffer-create "*foo*") (delete-region (point-min) (point-max)) (insert "foo\nbar\nfoo\n") (save-restriction (narrow-to-region (line-beginning-position -1) (line-end-position -1)) (error "" and typing M-x foo. In both cases, the buffer was not narrowed afterward. Can anyone else reproduce such a problem? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: eval-last-sexp narrows buffer on error
Calling `eval-last-sexp' on: "\u" correctly causes the error "Non-hex digit used for Unicode escape", but unexpectedly leaves the buffer narrowed to point-min and point. It does not fail for me. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: eval-last-sexp narrows buffer on error
> I've tried. From what I can tell `specpdl' isn't being wound back > afterwards, so `save_restriction_restore' is never called. > > In fact, this apparently is the case after any error (unless caught by > `condition-case'), so `specpdl' grows bigger and bigger. Is that > supposed to happen?? > > The functions called by `error' are > * signal > ** find_handler_clause > *** call_debuger I'm too silly. Try to run with `debug-on-error' and `eval-expression-debug-on-error' both nil. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: eval-last-sexp narrows buffer on error
martin rudalics <[EMAIL PROTECTED]> writes: > It's a problem with `save-restriction'. Take: > > (with-current-buffer (get-buffer-create "*foo*") > (delete-region (point-min) (point-max)) > (insert "foo\nbar\nfoo\n") > (save-restriction > (narrow-to-region (line-beginning-position -1) (line-end-position -1)) > (error ""))) > > It will leave the buffer narrowed although the doc-string of > `save-restriction' says: > > AFAICT Emacs 20 DTRT here, Emacs 21 and 22 don't. Could you try to > debug it? I've tried. From what I can tell `specpdl' isn't being wound back afterwards, so `save_restriction_restore' is never called. In fact, this apparently is the case after any error (unless caught by `condition-case'), so `specpdl' grows bigger and bigger. Is that supposed to happen?? The functions called by `error' are * signal ** find_handler_clause *** call_debuger debug * recursive-edit ** command_loop *** internal_catch command_loop_2 from which it never returns. regards, Nikolaj Schumacher ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Regexp not stateless?
I have just seen a state problem with regexps. I am not able to isolate the problem completely at the moment, but here is a sketch of it: I have this regexp: (defconst mumamo-script-tag-start-regex (rx ""))) ">" (optional (0+ space) "
Re: mail-abbrev-end-of-buffer apparently does nothing
Does this fix it? *** mailabbrev.el 21 Jan 2007 01:36:15 -0500 1.82 --- mailabbrev.el 28 Apr 2007 21:05:27 -0400 *** *** 494,499 --- 494,501 ;; the usual syntax table. (or (and (integerp last-command-char) + ;; Do let Ctl and Meta chars expand if they try. + (not (event-modifiers last-command-char)) (or (eq (char-syntax last-command-char) ?_) ;; Don't expand on @. (memq last-command-char '(?@ ?. ?% ?! ?_ ?- ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: filling long html href
Your code seems good. If people find the 1100 character regexp works well in practice, we could install your code after the release. Please bring it up again in a few months. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: python.el
Not easily in detail. Anything I actually contributed I consider OK, obviously. We need to verify that this is ok. When you wrote that code, did you have an employer who could possibly claim copyright on it? If so, do we have a disclaimer from that employer? This is why I ask the period of years during which you worked for that problematical employer, and the period of years during which you worked on the code in python.el. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs-22.0.99 configure problem
Jan Djärv <[EMAIL PROTECTED]> writes: > Does it work if you do > > % /bin/sh configure It has same problem. % /bin/sh configure as_func_failure succeeded. as_func_failure succeeded. No shell found that supports shell functions. Please tell [EMAIL PROTECTED] about your system, including any error possibly output before this message checking build system type... i386-unknown-freebsd6.2 checking host system type... i386-unknown-freebsd6.2 checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for AIX... ^Z zsh: suspended /bin/sh configure % ps PID TT STAT TIME COMMAND 61924 p0 Ss 0:00.13 -zsh (zsh) 72936 p0 T 0:00.11 /usr/local/bin/zsh configure 73340 p0 R+ 0:00.00 ps I figure out that setting SHELL environment variable to /bin/sh works. % SHELL=/bin/sh ./configure If login shell is zsh, login(1) is automatically set SHELL to /usr/local/bin/zsh. So zsh user who does not install bash (see below) may have same problem. > % bash configure > > if you have bash? I've installed bash. /bin/sh configure uses bash somehow. kageroh% /bin/sh configure checking build system type... i386-unknown-freebsd6.2 checking host system type... i386-unknown-freebsd6.2 checking for gcc... gcc checking for C compiler default output file name... a.out [...] checking for install-info... (cached) /usr/bin/install-info checking for gzip... /usr/bin/gzip checking for -znocombreloc... ^Z zsh: suspended /bin/sh configure kageroh% ps PID TT STAT TIME COMMAND 61924 p0 Ss 0:00.15 -zsh (zsh) 85481 p0 T 0:00.16 /usr/local/bin/bash configure 85976 p0 T 0:00.00 /usr/local/bin/bash configure 85977 p0 R+ 0:00.00 ps % echo $SHELL /usr/local/bin/zsh -- Hiroshi Fujishima ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: C- doesn't respect current keyboard layout, OS X Carbon
Ar an ceathrú lá is fiche de mí Aibréan, scríobh YAMAMOTO Mitsuharu: > > On Tue, 24 Apr 2007 10:29:38 +0200, Aidan Kehoe <[EMAIL PROTECTED]> > > said: > > >> Can you replace `action=' at line 722 with `output=' and try again? > > > There’s no action= at line 722--you’re talking about > > ExtendedIrishAidan.keylayout, available in the same directory. > > Oops, sorry. Yes, what I downloaded was ExtendedIrishAidan.keylayout. > I reached it by following a link in > http://www.parhasard.net/keyboard/, because I couldn't find > http://www.parhasard.net/keyboard/ExtendedAidan.layout. > > Does the modified ExtendedIrishAidan.keylayout have the same problem? http://www.parhasard.net/keyboard/ExtendedAidan.keylayout , the keyboard layout I was talking about in the first place, and the most recent version of the file, has the problem. > > I don’t get any error messages in console.log when I log in with > > ExtendedAidan.keylayout . > > Neither do I. But I couldn't reproduce the problem with US keyboard. The keyboard hardware should be irrelevant. Okay, I did a cvs update and updated my OS (I was previously running 10.4.7, am now runnibng 10.4.9), and I no longer see the problem, whether with my layout or Nikolaj’s. Thank you for your attention! -- On the quay of the little Black Sea port, where the rescued pair came once more into contact with civilization, Dobrinton was bitten by a dog which was assumed to be mad, though it may only have been indiscriminating. (Saki) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: eval-last-sexp narrows buffer on error
> Calling `eval-last-sexp' on: > "\u" > correctly causes the error "Non-hex digit used for Unicode escape", but > unexpectedly leaves the buffer narrowed to point-min and point. It's a problem with `save-restriction'. Take: (with-current-buffer (get-buffer-create "*foo*") (delete-region (point-min) (point-max)) (insert "foo\nbar\nfoo\n") (save-restriction (narrow-to-region (line-beginning-position -1) (line-end-position -1)) (error ""))) It will leave the buffer narrowed although the doc-string of `save-restriction' says: The old restrictions settings are restored even in case of abnormal exit (throw or error). AFAICT Emacs 20 DTRT here, Emacs 21 and 22 don't. Could you try to debug it? You can side-step the problem with something like (with-current-buffer (get-buffer-create "*foo*") (delete-region (point-min) (point-max)) (insert "foo\nbar\nfoo\n") (condition-case err (save-restriction (narrow-to-region (line-beginning-position -1) (line-end-position -1)) (error "")) (error err (widen) (error (error-message-string err) which does the wrong thing when the buffer was already narrowed before executing the `save-restriction' form. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
