Hi,
> I've committed the update (after testing it myself, on 10.5). Look for
> revision 105.
It works now. Thanks to all!
Best wishes,
Ingo
--
==
Ingo Thies
Argelander-Institut fuer Astronomie (AIfA)
Sternwarte, University of Bonn
Auf dem Huegel 71, D-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/10 6:15 PM, Sebastien Maret wrote:
> Hi Remi,
>
> Le 19 avr. 2010 à 22:12, Remi Mommsen a écrit :
>
>> Hi,
>>
>> On Apr 19, 2010, at 9:31 PM, Alexander Hansen wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 4/19/10
Hi Remi,
Le 19 avr. 2010 à 22:12, Remi Mommsen a
écrit :
> Hi,
>
> On Apr 19, 2010, at 9:31 PM, Alexander Hansen wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 4/19/10 3:05 PM, Ingo Thies wrote:
>>> Hi again,
>>>
maintainer to see whether he knows anything about it?
Hi,
On Apr 19, 2010, at 9:31 PM, Alexander Hansen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 4/19/10 3:05 PM, Ingo Thies wrote:
>> Hi again,
>>
>>> maintainer to see whether he knows anything about it? And have you seen
>>> anything in the emacs bug reporting avenues?
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/10 3:05 PM, Ingo Thies wrote:
> Hi again,
>
>> maintainer to see whether he knows anything about it? And have you seen
>> anything in the emacs bug reporting avenues?
>
> Just found (after adding &num=100 in the Google URL) an entry:
>
> ht
Hi,
> Sounds plausible: gtk+2 did get updated recently.
I've sent another e-mail to Sebastian Maret including the Link.
I've tested the M-x accelerate menu trick; it updates the buffer list
only once; you have to re-use this command each time you wish the list to
be updated. So, unfortunately
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/10 3:05 PM, Ingo Thies wrote:
> Hi again,
>
>> maintainer to see whether he knows anything about it? And have you seen
>> anything in the emacs bug reporting avenues?
>
> Just found (after adding &num=100 in the Google URL) an entry:
>
> ht
Hi again,
> maintainer to see whether he knows anything about it? And have you seen
> anything in the emacs bug reporting avenues?
Just found (after adding &num=100 in the Google URL) an entry:
http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=4122
Bug #4122 describes very accurately
