In article <[EMAIL PROTECTED]>, Peter Dyballa <[EMAIL PROTECTED]> writes:
> 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 =
> I fixed this last night, I think. Does it work now?
Thanks, it works now.
Have you noticed that read-only matches are highlighted by lazy-highlight
even though perform-replace skips them? This is very misleading.
Do you think this should be fixed?
A patch I proposed a few months ago could fi
> OK, I can see it will never work in the help buffer. I've installed your
> fix (almost): help-insert-string just sets help-xref-stack-item rather than
> call help-setup-xref.
Thanks. I just installed more minor fixes.
> If it still doesn't work, then please fix it as you see fit. Although
>
On Tue, 27 Dec 2005 18:14:02 -0500 Richard M. Stallman wrote:
> I fixed this last night, I think. Does it work now?
It's working. Thank you for fixing this.
David
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/ma
HI,
> [Mon, 26 Dec 2005 14:35:42 -0800]
> Bill Wohler <[EMAIL PROTECTED]> writes:
> While chasing down a problem with the setting of
> url-configuration-directory, I wanted to update loaddefs.el, but look at
> the error:
[...]
> Wrong type argument: symbolp, 0
> make: *** [autoload
1) Keep an index with line numbers for every 5000th character in a
buffer and use the index to get a good approximate translation from
char-position to line number (or char-position to pixel height count,
This might work fast enough to be usable--I guess we could try it if
someon
I fixed this last night, I think. Does it work now?
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
> > I made two commits within a couple of hours. Have you picked up the latest
> > version of descr-text.el (1.48)?
>
> Yes, I tested the latest version. Try to use `describe-char' on any
> character in the help buffer.
OK, I can see it will never work in the help buffer. I've installed yo
> I can see a point to your proposition to save the whole buffer content, tho
> I'd do it generically in help-setup-xref:
> [...]
> and then update all uses of help-xref-stack-item.
I think this would be a good generic solution.
> But I also like the current behavior which recomputed the contents
> My point is that the doc string of `with-temp-file' says that
> a new buffer is _created_, used to evaluate stuff, and then
> written to its file. It says nothing about the buffer being
> _temporary_ (i.e., being deleted after being saved).
Indeed it doesn't say so. I don't
> My point is that the doc string of `with-temp-file' says that a new buffer
> is _created_, used to evaluate stuff, and then written to its file.
> It says nothing about the buffer being _temporary_ (i.e., being deleted
> after being saved).
Indeed it doesn't ay so. I don't find it indispensable
> The doc string of with-temp-file should mention that the new buffer
> created is killed at the end.
> I tried to do this:
> (unwind-protect
> (with-temp-file "foo" (pp something (current-buffer)))
> (kill-buffer "foo"))
You seem to also be confusing it with `w
> 1) Keep an index with line numbers for every 5000th character in a buffer
>and use the index to get a good approximate translation from
>char-position to line number (or char-position to pixel height count,
>i.e. lines x char-height) by using the index and counting the remaining
>
>>> This is not reliable way to restore the old output of `describe-char'
>>> since the original buffer might be killed or the character at the old
>>> position might be deleted,
>>
>> The same holds for most/all other uses of help-setup-xref.
> So it makes sense to preserve the original contents
> The doc string of with-temp-file should mention that the new buffer
> created is killed at the end.
> I tried to do this:
> (unwind-protect
> (with-temp-file "foo" (pp something (current-buffer)))
> (kill-buffer "foo"))
You seem to also be confusing it with `with-temp-buffer'.
> > Now I see a new argument `buf' was added to `describe-char' in CVS.
> > This doesn't work even for normal uses of the help buffer. Clicking
> > on any link in the help buffer created by `describe-char' and going
> > back produces nonsense, because it tries to restore the old contents
> >
On 25 Dec 2005, at 20:06, Richard M. Stallman wrote:
The length of the slider bar, the blue bar that slides inside
the scroll bar track (I'm not sure about the terminology) changes
randomly as you scroll up and down the text. I'm sure you know that
the ratio of the length of this bar to t
17 matches
Mail list logo
