Chong Yidong [EMAIL PROTECTED] writes:
This is a strange one. Evaluate the following two functions. Both of
them should do the same thing: replace each of the first 3 letters
in the buffer with the letter A.
(defun foo ()
(interactive)
(let ((pos '(1 2 3)))
(while pos
(defun foo ()
(interactive)
(let ((pos '(1 2 3)))
(while pos
(put-text-property (car pos) (1+ (car pos)) 'display A)
(setq pos (cdr pos)
(defun bar ()
(interactive)
(progn (put-text-property 1 2 'display A)
(put-text-property 2
(eq (substring fred 0 1) (substring fred 1 2))
nil
`substring' creates/allocates a string, so (eq (substring ...) ...) will
*always* return nil.
`eq' is pointer equality, whereas `equal' is structural equality.
Stefan
___
Emacs-pretest-bug
Forget the substring example, dotimes works like while in foo, but it still
doesn't seem right.
(setq b '())
nil
(dotimes (i 2)
(push a b))
nil
(eq (car b) (cadr b))
t
(setq b '())
nil
(push a b)
(a)
(push a b)
(a a)
(eq (car b) (cadr b))
nil
Nick
Type M-x foo. You end up with
A45
This is because the `display' property of all three characters is eq.
With bar, they are three different strings.
I will document this in the manual.
___
Emacs-pretest-bug mailing list
Stefan Monnier [EMAIL PROTECTED] writes:
That isn't correct. There is a comment somewhere in the doc or code
about quotation marks intentionally _not_ having string syntax in text
modes or globally.
Which comment in which code?
I don't know, or I'd have referenced it. I guess rms can
Kenichi Handa [EMAIL PROTECTED] writes:
I don't join this discussion anymore because I have no
knowledge about the usage of those characters.
But you don't need such knowledge personally -- it is written down,
especially in Unicode. I certainly don't know much of the languages
I've provided
The encoding of a utf-16 file isn't detected correctly when finding
the file.
To reproduce: push 'coding-category-utf-16-le onto
`coding-category-list', and put foo into a new buffer. C-x h and
M-x encode-coding-region mule-utf-16le-with-signature. Then,
correctly:
(detect-coding-region 1
What I currently see in my Lucid menu is a question mark. Is that what you
mean by junk?
No, I meant basically random characters. Question marks would be
better. Maybe something has changed; I can't check at present. I
can't remember how it is (or was) and what cleanup was rejected, but
That isn't correct. There is a comment somewhere in the doc or code
about quotation marks intentionally _not_ having string syntax in text
modes or globally.
Which comment in which code?
I don't know, or I'd have referenced it. I guess rms can comment on
the intent.
I guess this answer
Type C-x and let it echo. Then type RET. It's echoed as `C-x RET',
not `C-x RET-', as it should be, so it's not clear the input is
incomplete. This is under GTK or tty.
___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
Dave Love [EMAIL PROTECTED] writes:
There's no browse-url support for firefox.
Did you see my patch to emacs-devel a few days ago? Looking for
comments. Perhaps it is harmless, and I can install.
http://article.gmane.org/gmane.emacs.devel/34370
Also `browse-url-default-browser' should look
Myabe this is what Emacs should do, create a pixmap, do its drawing
there, and then XCopyArea it to the window when done.
Why do you think Emacs should do this? What benefit would it provide?
I can't see any.
It reduces/eliminates flicker during redraw. But if the problem can be
solved
Forget the substring example, dotimes works like while in foo, but it still
doesn't seem right.
What doesn't seem right about it? It's bog-standard behavior.
In your (2nd) dotimes example, a only occured once in the source,so
there's really only one object a.
In the two
First, I have to apologize to Richard and anyone else who took time
with my bug report under the subject Debugging with match data: as
Richard implied and I now confirm, the bug I reported doesn't occur
with Emacs -Q. My only excuse is that I really did think I had tested
it with Emacs -Q, but
From my previous message:
Many other interactive languages indeed read _and_ execute
repeatedly in loops as well as in function calls, producing many
non-identical objects.
I should have said Some other interactive languages. I do not know
what percentage of interactive languages do what
Nick Roberts wrote:
As someone who doesn't have a background in Lisp, I would expect executing
the same statement three times to give the same result as executing three
identical statements.
I guess that with executed three times you mean read and evaluated
three times. The way I
As someone who doesn't have a background in Lisp, I would expect executing
the same statement three times to give the same result as executing three
identical statements. Perhaps its a bit like quantum mechanics, in that,
once you've passed the stage of disbelief, you can no longer see what
Open a new file and insert the following text upto and including the
line This is a test an the following blank line.
1. Now is the time for all good men to come to the aid of their party.
2. Now is the time for all good men to come to the aid of their party.
3. Now is the time for all good men
19 matches
Mail list logo
