Re: Saving SVN-managed files over Tramp fails
Magnus Henoch [EMAIL PROTECTED] writes: I had opened a file on a remote host over Tramp. The file is in an SVN tree. When trying to save the file, I get the following backtrace. (I don't have SVN installed on the local machine) I've tried to reproduce the peoblem locally. `vc-do-command' returns with an error only when the default-directory is not the remote svn directory. Since you are simply saving, this shouldn't be your case. I've also debugged vc-do-command, there shouldn't be a need for a local svn command (vc-do-command calls process-file). So could you, please, replay the scenario and raise a Tramp bug report? tramp-verbose should be 10, and the Tramp debug buffer would be valuable. Best regards, Michael. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs -Q behavior doesn't match doc
While trying to document a bug I ran Emacs using -Q. It was a nice surprise to see syntax highlighting and paren matching were on. I've always thought these should default to ON. But the doc specifically says ... This is like using `-q' and `--no-site-file', but in addition it also disables the menu-bar, the tool-bar, the scroll-bars, tool tips, the blinking cursor, and the fancy startup screen. Could you state precisely which exact docs are you referring to? `emacs --help' gives: --quick, -Q equivalent to -q --no-site-file --no-splash and `(emacs)Initial Options' says: `-Q' `--quick' Start emacs with minimum customizations. This is like using `-q' and `--no-site-file', but also disables the startup screen. Since you are apparently using relatively recent CVS: GNU Emacs 22.0.50.1 (i386-msvc-nt5.1.2600) of 2005-11-11 on LD1 that is what you should see, unless there is a problem with the way you updated. But maybe you are referring to some other docs that we might indeed have overlooked. Sincerely, Luc. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Begging for show-paren change???
Will any amount of begging get me this show-paren change? I've now got 4 major modes (tal, tacl, ddl, cobol) supporting language constructs that can't be described by the limited paren matching ability of show-paren-function in paren.el. Currently any given character can only match one specific other character. So in a simple example, the B of BEGIN can only match the d of End and can't also match D if END spelled with an upper case D. In tal-mode B b need to match one of D, d, ;, K, k depending on circumstance while D and d need to match one of B, b or ;. Adding the 3 lines below would yield the needed flexibility in a straightforward way. It allows matching on the value of the syntax cdr itself. If you think about it, this is probably how it should have worked from the start. The example uses negative numbers to prevent impact to existing code. Some positive number range will work, as will (symbolp (cdr (syntax-after beg))). I've tried all these ways with success. Anything is fine for me. I'd like to be able to finally release these modes in working condition with 22.1. Example snip from font-lock-syntactic-keywords: (\\(?:^\\|\\s-\\)\\(d\\)efine\\(?:\\s-\\|$\\)(1 (4 . -101))) (\\(?:^\\|\\s-\\)\\(b\\)egin\\(?:\\s-\\|:\\|$\\) (1 (4 . -102))) (#\\(;\\)(1 (5 . -101))) (\\(?:\\s-\\|^\\)en\\(d\\)\\b(1 (5 . -102))) (defun show-paren-function () ... (setq mismatch (not (or (eq (char-before end) ;; This can give nil. (cdr (syntax-after beg))) (eq (char-after beg) ;; This can give nil. (cdr (syntax-after (1- end + (and ( 0 (+ 0 (cdr (syntax-after beg + (eq (cdr (syntax-after (1- end))) + (cdr (syntax-after beg) Richard Bielawski ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs -Q behavior doesn't match doc
While trying to document a bug I ran Emacs using -Q. It was a nice surprise to see syntax highlighting and paren matching were on. I've always thought these should default to ON. But the doc specifically says ... This is like using `-q' and `--no-site-file', but in addition it also disables the menu-bar, the tool-bar, the scroll-bars, tool tips, the blinking cursor, and the fancy startup screen. Could you state precisely which exact docs are you referring to? I'm not up to snuff on figuring out where the source is but the section I quoted starts like this: C.2 Initial Options === The initial options specify parameters for the Emacs session. This section describes the more general initial options; some other options specifically related to the X Window System appear in the following sections. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs -Q behavior doesn't match doc
I'm not up to snuff on figuring out where the source is but the section I quoted starts like this: C.2 Initial Options === The initial options specify parameters for the Emacs session. This section describes the more general initial options; some other options specifically related to the X Window System appear in the following sections. Your Info version of the Elisp manual is not up to date. I guess you ran: $ ./configure $ make $ cd lisp $ make recompile EMACS=../src/emacs $ cd .. $ make as recommended in INSTALL.CVS. I thought that `make' automatically updates the Info docs, but I am not really sure of that. I am sure that somebody else on this list will know. I personally always do `make maintainer-clean', `configure' and `make bootstrap', which does update them. Sincerely, Luc. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs -Q behavior doesn't match doc
From my earlier reply: Your Info version of the Elisp manual is not up to date. I meant: Your Info version of the Emacs manual is not up to date. Sincerely, Luc. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Crash during access_keymap
On 13 Nov 2005, at 06:39, YAMAMOTO Mitsuharu wrote: So, if there's a non-pure object that is only pointed to by pure objects, which may happen if the assumption for the pure storage is violated, then the object is reachable but get collected. OK, that makes sense. Do you know if this is documented somewhere? I've read the info nodes about pure storage etc., and it doesn't say anything about what to look for in code, or if there is a way to test for the effect while loading. Maybe on a port that implements memory protection? I mostly just preload code, but define a setup function in each package that is run at runtime. But from what you are saying, I am getting that vectors are allocated when the file is loaded, and not copied when a function is called. But if the code used (vector 0 0 0 0 0) instead of [0 0 0 0 0], the vector would be allocated at runtime and we don't run into such trouble. Does this apply only to vectors? (Since vectors seem immutable to me, this all would make sense...) Any pointers to documentation would be greatly appreciated - I'm happy to read whatever there is. Thanks - David ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs -Q behavior doesn't match doc
But the doc specifically says ... This is like using `-q' and `--no-site-file', but in addition it also disables the menu-bar, the tool-bar, the scroll-bars, tool tips, the blinking cursor, and the fancy startup screen. That statement is incorrect. Where _exactly_ is it? You said the doc, which is not very specific. I can change it if I can find it. So please tell me me the file name and line number. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Warnings during compilation
I will fix many of these. I asked others to look at some. I did not get the warnings from printing.el. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: erase customization does not work
If i choose 'erase customization' in a customization buffer i get the following message: widget-apply: Symbol's function definition is void: nil I can't reproduce that. Would you please provide a _precise_ test case? Please read the Bugs section in the Emacs manual, which provides guidelines on how to write a bug report to give us the necessary information so we can fix the bug. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: set-window-point
The disassembly buffer appears in its own frame as a dedicated window with frame focus and Emacs makes this window selected. The cursor is at the start of the buffer and Edebug shows that set-window-point doesn't move it. Is the disassembly buffer the current buffer at the time? Perhaps the problem case is where the window is selected but the buffer is not current. Can you find out if this is so? ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Begging for show-paren change???
The example uses negative numbers to prevent impact to existing code. Some positive number range will work, as will (symbolp (cdr (syntax-after beg))). I've tried all these ways with success. Anything is fine for me. I'd like to be able to finally release these modes in working condition with 22.1. I think we don't need to assume these things are numbers or anything. We can just check (eq (cdr (syntax-after (1- end))) (cdr (syntax-after beg))) which will work for negative integers, symbols, positive ints, ... After all, the two chars are related by the fact that forward-sexp jumps from one to the other, so it's extremely unlikely that the above check would ever return a wrong answer (i.e. say that the two chars are correctly matched when they are not). For such an error to occur we'd need a syntax where char CHAR1 has syntax (a and the other CHAR2 has )a and that they do not match. I.e. a is expected to both close CHAR1 and to open CHAR2 (so the syntax of a needs to be sometimes ( and sometimes )) and CHAR2 does not close CHAR1. Can't think of any scenario where this could occur. So I just suggest the patch below instead. Stefan --- paren.el20 aoû 2005 19:26:11 -0400 1.64 +++ paren.el13 nov 2005 17:37:23 -0500 @@ -181,7 +181,12 @@ (cdr (syntax-after beg))) (eq (char-after beg) ;; This can give nil. - (cdr (syntax-after (1- end) + (cdr (syntax-after (1- end + ;; The cdr might hold a new paren-class + ;; info rather than a matching-char info, + ;; in which case the two CDRs should match. + (eq (cdr (syntax-after (1- end))) + (cdr (syntax-after beg ;; ;; Highlight the other end of the sexp, or unhighlight if none. (if (not pos) --- simple.el 12 Nov 2005 00:10:56 - 1.762 +++ simple.el 13 Nov 2005 22:38:39 - @@ -4314,9 +4314,8 @@ (eq (syntax-class syntax) 4) (cdr syntax) (cond -((or (null matching-paren) - (/= (char-before oldpos) - matching-paren)) +((not (or (eq matching-paren (char-before oldpos)) + (eq matching-paren (cdr (syntax-after oldpos) (message Mismatched parentheses)) ((not blinkpos) (if (not blink-matching-paren-distance) ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: set-window-point
The disassembly buffer appears in its own frame as a dedicated window with frame focus and Emacs makes this window selected. The cursor is at the start of the buffer and Edebug shows that set-window-point doesn't move it. Is the disassembly buffer the current buffer at the time? Perhaps the problem case is where the window is selected but the buffer is not current. Can you find out if this is so? Yes, you're right. If I use the patch below it works. Shall I install it, or is it a bug in set-window-point? If it's not a bug, I think this behaviour should be documented. Nick *** gdb-ui.el 13 Nov 2005 21:31:16 +1300 1.111 --- gdb-ui.el 14 Nov 2005 12:29:46 +1300 *** *** 2702,2708 (if (re-search-forward address nil t) (gdb-put-breakpoint-icon (eq flag ?y) bptno (if (not (equal gdb-frame-address main)) ! (set-window-point (get-buffer-window buffer 0) pos (defvar gdb-assembler-mode-map (let ((map (make-sparse-keymap))) --- 2702,2709 (if (re-search-forward address nil t) (gdb-put-breakpoint-icon (eq flag ?y) bptno (if (not (equal gdb-frame-address main)) ! (with-current-buffer (gdb-get-buffer 'gdb-assembler-buffer) ! (set-window-point (get-buffer-window buffer 0) pos) (defvar gdb-assembler-mode-map (let ((map (make-sparse-keymap))) ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs -Q behavior doesn't match doc
I get a Don't know how to make maintainer-clean message when I run `nmake maintainer-clean'. I made the mistake of locating a makefile that DID know how and it emptied my emacs\info directory. nmake bootstrap completes successfully but it never rebuilds the info files. It does rebuild them. But you may have to run `make install' after `make bootstrap' to install them in the place an installed Emacs looks for them. make maintainer-clean ./configure make bootstrap sudo make install should have properly updated all your info files as well as everything else. Sincerely, Luc. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: No i-search for € in iso-8859-16 coded buffer
In a buffer starting with ';;; -*- mode: Text; coding: iso-8859-16; -*-' (-r: in the mode-line) and holding the characters in the range 160-255 i-search for € is not successful: € = 244 = 164 = A4 = U+20AC = E2 82 AC : EURO SIGN That's because ISO-8859-15 (Latin-9) is coded internally with latin-iso8859-15 charset, but ISO-8859-16 (Latin-10) is coded with mule-unicode-0100-24ff charset. I don't know a reason for this decision. Perhaps there are some ISO-8859-16 characters that exist only in mule-unicode-0100-24ff, and not in any of latin-iso8859-... charsets. -- Juri Linkov http://www.jurta.org/emacs/ ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: No i-search for € in iso-8859-16 coded buffer
2005/11/14, Juri Linkov [EMAIL PROTECTED]: character: € (01235114, 342604, 0x53a4c, U+20AC) ... I think it was a good change to use lisp-readable syntax for `M-:', so the same syntax should be used for `C-x =' as well. Yeah... Is there a lisp syntax for U+20AC? -miles -- Do not taunt Happy Fun Ball. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs -Q behavior doesn't match doc
But I don't see configure looking for makeinfo It looks for install-info. so I don't see how this should happen. It is `make bootstrap' that calls makeinfo, not configure. But maybe the following excerpt of INSTALL.CVS is relevant, if you are using MS Windows: Users of non-Posix systems (MS-Windows etc.) should run the platform-specific configuration scripts (nt/configure.bat, config.bat, etc.) before make bootstrap. I do not really know anything about MS Windows. Sincerely, Luc. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs -Q behavior doesn't match doc
But I don't see configure looking for makeinfo It looks for install-info. That doesn't seem useful. If the user doesn't have makeinfo available on their path the make will fail. so I don't see how this should happen. It is `make bootstrap' that calls makeinfo, not configure. But if you don't have makeinfo the makefile's for man, lispref and lispintro will fail. It seems to me the function of configure is to see what the compile environment looks like. At the moment neither checks. So to prevent a failure those make files aren't called. Users of non-Posix systems (MS-Windows etc.) should run the platform-specific configuration scripts (nt/configure.bat, config.bat, etc.) before make bootstrap. Naturally I do that or Emacs itself probably wouldn't compile. After studying the makefile I believe I've discovered a workaround. nmake clean -- seems to do on NT what maintainer-clean does on unix call configure nmake bootstrap nmake info -- you would only do this if you have makeinfo installed nmake install If this is correct, calling 'nmake info' should probably be documented for NT builds. Either that or it should be called during 'make bootstrap' if makeinfo is accessible. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs -Q behavior doesn't match doc
But if you don't have makeinfo the makefile's for man, lispref and lispintro will fail. For CVS, you need version 4.2 or later of Texinfo. Sincerely, Luc. ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: set-window-point
*** gdb-ui.el 13 Nov 2005 21:31:16 +1300 1.111 --- gdb-ui.el 14 Nov 2005 12:29:46 +1300 *** *** 2702,2708 (if (re-search-forward address nil t) (gdb-put-breakpoint-icon (eq flag ?y) bptno (if (not (equal gdb-frame-address main)) ! (set-window-point (get-buffer-window buffer 0) pos (defvar gdb-assembler-mode-map (let ((map (make-sparse-keymap))) --- 2702,2709 (if (re-search-forward address nil t) (gdb-put-breakpoint-icon (eq flag ?y) bptno (if (not (equal gdb-frame-address main)) ! (with-current-buffer (gdb-get-buffer 'gdb-assembler-buffer) ! (set-window-point (get-buffer-window buffer 0) pos) (defvar gdb-assembler-mode-map (let ((map (make-sparse-keymap))) I don't understand the above code: what's the relationship between `buffer' and `(gdb-get-buffer 'gdb-assembler-buffer)' ? Also, how do you know that (get-buffer-window buffer 0) is non-nil? Stefan ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: set-window-point
Stefan Monnier writes: *** gdb-ui.el 13 Nov 2005 21:31:16 +1300 1.111 --- gdb-ui.el 14 Nov 2005 12:29:46 +1300 *** *** 2702,2708 (if (re-search-forward address nil t) (gdb-put-breakpoint-icon (eq flag ?y) bptno (if (not (equal gdb-frame-address main)) ! (set-window-point (get-buffer-window buffer 0) pos (defvar gdb-assembler-mode-map (let ((map (make-sparse-keymap))) --- 2702,2709 (if (re-search-forward address nil t) (gdb-put-breakpoint-icon (eq flag ?y) bptno (if (not (equal gdb-frame-address main)) ! (with-current-buffer (gdb-get-buffer 'gdb-assembler-buffer) !(set-window-point (get-buffer-window buffer 0) pos) (defvar gdb-assembler-mode-map (let ((map (make-sparse-keymap))) I don't understand the above code: what's the relationship between `buffer' and `(gdb-get-buffer 'gdb-assembler-buffer)' ? Also, how do you know that (get-buffer-window buffer 0) is non-nil? Yes, buffer is (gdb-get-buffer 'gdb-assembler-buffer) so I should have had (with-current-buffer buffer... I'm just saying that I can make the buffer of the selected window current so that set-window-point works. If (get-buffer-window buffer 0) (buffer = gdb-assembler-buffer) is nil, gdb-assembler-custom shouldn't get called. Nick ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Crash during access_keymap
So, if there's a non-pure object that is only pointed to by pure objects, which may happen if the assumption for the pure storage is violated, then the object is reachable but get collected. Is there evidence that this is in fact happening? If so, can you see a general rule for how to prevent it from happening? ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Crash during access_keymap
On Sun, 13 Nov 2005 19:24:34 +, David Reitter [EMAIL PROTECTED] said: On 13 Nov 2005, at 06:39, YAMAMOTO Mitsuharu wrote: So, if there's a non-pure object that is only pointed to by pure objects, which may happen if the assumption for the pure storage is violated, then the object is reachable but get collected. OK, that makes sense. Do you know if this is documented somewhere? I'm not sure if it is explicitly documented. I just read src/alloc.c. The function `mark_object' immediately returns if its argument is a pure object. I've read the info nodes about pure storage etc., and it doesn't say anything about what to look for in code, or if there is a way to test for the effect while loading. Maybe on a port that implements memory protection? Setting watchpoint to the variable `pure' will do run-time check. It is really feasible in GDB on Mac OS X thanks to hardware watchpoints. I mostly just preload code, but define a setup function in each package that is run at runtime. But from what you are saying, I am getting that vectors are allocated when the file is loaded, and not copied when a function is called. But if the code used (vector 0 0 0 0 0) instead of [0 0 0 0 0], the vector would be allocated at runtime and we don't run into such trouble. Yes, but a vector is created on every call then. Does this apply only to vectors? (Since vectors seem immutable to me, this all would make sense...) Literal strings and conses, as well as several vector-like objects. I don't understand what vectors seem immutable means above. Vectors are mutable in the sense that one can alter their contents. YAMAMOTO Mitsuharu [EMAIL PROTECTED] ___ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
