headers
Lennart Borgman (gmail | 1 Jun 2008 01:09
Picon
Gravatar

Re: Three strikes them out

martin rudalics wrote:
>  > Does that mean I have to arrange to avoid after-change-functions to be
>  > run during fontification?
> 
> I'm afraid I don't understand your question.  Font-lock routines bind
> `inhibit-modification-hooks' to t so these won't be run during
> fontification.

Ah, thanks. That was not clear to me.

 > I suppose you use some other hook or timer based code
> that modifes the buffer and triggers contextual fontification over and
> over.

This time I happened to change the text property 'fontified (because of 
a test I forgot to remove). But the hang I experienced during this did 
not lock up Emacs totally.

Thinking about it again that is what I expect since the loops involved 
restarting idle timers.
Permalink | Reply | 0 comments |
headers
Lennart Borgman (gmail | 1 Jun 2008 01:19
Picon
Gravatar

Re: Three strikes them out

martin rudalics wrote:
>  > I agree with Lennart that Emacs should provide more facilities to get
>  > out of awkward situations. Sure, fix the bug, but how is any given Emacs
>  > user affected by some Emacs bug somewhere supposed to do that?
> 
> If the bug is with Emacs' fontification routines there's hardly anything
> a user can do but give a simple and precise recipe to reproduce the bug
> and wait until someone familiar with the code fixes it.  At least that's
> what I would do.

And it is still very hard to find those bugs sometimes. One suggestion 
that have been given here to test fontification code is to run it by 
calling for example font-lock-fontify-region.

That does not always work because that function fontifies from top to 
bottom, but the bug may perhaps only show up in other situations.

I think it would be useful to be able to set `debugger' to something 
that can log an error during fontification. That is currently not possible.

>  > Lennarts "c-g repeatedly" maybe wasnt the best example. Surely this
>  > doesnt exclude the possibility of adding some other helpful feature?
> 
> If it's timer based it might depend on whether you're able to intercept
> it.

I just wanted a C-g signal to reach the timers just as it now reaches 
code running directly in the command loop. I thought that some C-g in a 
row would be easy to remember for that. (Of course some more things 
needs to be stopped for this to be meaningful. Timers should be stopped
(Continue reading)

Permalink | Reply | 4 comments |
headers
NAKAJI Hiroyuki | 1 Jun 2008 01:59
Picon
Favicon

Re: cannot start Gnus with idna.el

Thank you for the comment.

After "make maintainer-clean" in emacs/lisp directory, I successfully
bootstrapped the latest emacs. And then I'm trying this problem again.

>>>>> In <v9y75z98of.fsf <at> marauder.physik.uni-ulm.de> 
>>>>>	Reiner Steib <reinersteib+gmane <at> imap.cc> wrote:

> > The "while" in idna-to-ascii-response() seems infinite loop.
> >
> > (defun idna-to-ascii-response ()
> >   (while (and (eq (process-status idna-to-ascii-process) 'run)
> >               (null idna-to-ascii-response))
> >     (accept-process-output idna-to-ascii-process 1))
> >   idna-to-ascii-response)

> Isn't this a bug in `idna.el' then?  Cc-ing Simon therefore.

I'm not sure.

> > The idna-to-ascii-response is called from message.el and the failure
> > itself occurs in
> >
> > (idna-to-ascii "räksmörgås")

> Does it mean, that you can reproduce the problem when evaluating this
> expression after starting "emacs -Q"?

No.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Miles Bader | 1 Jun 2008 03:25
Picon
Gravatar

Re: emacs' turn: remove useless if-before-free tests

Jim Meyering <jim <at> meyering.net> writes:
> SunOS4 is no longer supported or even used, so that's not an issue.

Er, SunOS 4 is still used here...

[Not that I really disagree with your patch, mind you...]

-Miles

--

-- 
Do not taunt Happy Fun Ball.
Permalink | Reply | 5 comments |
headers
Miles Bader | 1 Jun 2008 03:30
Picon
Gravatar

Re: Full screen mode on windows

Eli Zaretskii <eliz <at> gnu.org> writes:
>> I knew how to maximize with the w32-send-sys-command command. By full
>> screen I mean no title bar, no windows decoration and no taskbar.
>
> Why would you want such a thing?  If you don't want any GUI features
> at all, type Alt-RET into the Command Prompt window, and then invoke
> "emacs -nw".

Emacs without title bar, window decorations, or taskbar, is still
very different than emacs in a terminal...

-Miles

--

-- 
In New York, most people don't have cars, so if you want to kill a person, you
have to take the subway to their house.  And sometimes on the way, the train
is delayed and you get impatient, so you have to kill someone on the subway.
  [George Carlin]
Permalink | Reply | 0 comments |
headers
Miles Bader | 1 Jun 2008 03:36
Picon
Gravatar

Re: Three strikes them out

"Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com> writes:
> I just wanted a C-g signal to reach the timers just as it now reaches
> code running directly in the command loop. I thought that some C-g in a
> row would be easy to remember for that.

I think that would an _extremely_ bad idea -- I often hit C-g like crazy
when response is just the tiniest bit slow (or even simply because I'm
angry at something else).

If parts of emacs just stopped working, in invisible and hard to debug
ways, just because the user happened to hit C-g a few too many times, it
would be very annoying and confusing for users.

-Miles

--

-- 
Opportunity, n. A favorable occasion for grasping a disappointment.
Permalink | Reply | 1 comment |
headers
Jason Rumney | 1 Jun 2008 04:02
Picon

Re: Full screen mode on windows

Eli Zaretskii wrote:
>> From: joakim <at> verona.se
>> Date: Sat, 31 May 2008 14:53:58 +0200
>> Cc: emacs-devel <at> gnu.org
>>
>> I would suggest looking at the existing fullscreen option for X:
>>
>>       (set-frame-parameter nil 'fullscreen  'fullboth)
>>
>> and make that work for w32, if it doesnt already!
>>     
>
> It does work, although it only emulates the fullscreen mode.
>
> But 
>
>    (w32-send-sys-command #xf030)
>
> will do exactly what the OP wants.
>   

Neither the fullscreen parameter, nor the command above produce a full 
screen window. They both produce a maximised window that still contains 
the window decorations, and does not overlap the taskbar.
Permalink | Reply | 0 comments |
headers
Jason Rumney | 1 Jun 2008 04:08
Picon

Re: Mail that shuld not be sent here

Don Armstrong wrote:
> On Sat, 31 May 2008, Richard M Stallman wrote:
>   
>> I am sure that is true, but it makes no sense to make a lot of
>> people go to this trouble. Sending this mail to bug-gnu-emacs is a
>> bad default.
>>     
>
> It's a good default, but it may be improper for your project.
>   

The wording of the done messages makes it look like the message is 
intended only for the developer who closed it.
Can we change the wording? It should be just the body of the done mail, 
the developer will indicate in there that they have dealt with the 
report, so it shouldn't be necessary to add extra text. And the original 
report can be looked up if someone following the thread does not 
remember what it was about.
Permalink | Reply | 5 comments |
headers
Miles Bader | 1 Jun 2008 04:43
Picon
Gravatar

Re: face-remapping patch

Chong Yidong <cyd <at> stupidchicken.com> writes:
> I see.  I think the patch makes good sense.

Thanks  :-)

Since both maintainers seem to approve, and there have been no
substantive objections, I'll commit the patch.

-Miles

--

-- 
Arrest, v. Formally to detain one accused of unusualness.
Permalink | Reply | 0 comments |
headers
Florian Beck | 1 Jun 2008 04:47
Picon
Favicon

Re: 23.0.60; emacs-report-bug fails silently

"Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com> writes:

>>
>> Not that I know of. I never needed to and I would not know how to set
>> it up. As I said, now that I know about the problem, it is easy for me
>> to fix.
>>
>> Look, if you think my setup is bizzare, please ignore my report.
>
> No, I just wanted to be sure about what could be done.
>
> From what you have told us it looks like when
>
> - there is no way for Emacs to send the bug report itself
> - and there is no system mail client that can be used
>
> then Emacs pretends it still has sent the message. That is of course a
> bug that should be removed if it is possible.

Exactly.

> Though I am not at all sure what is happening on your system. On my
> w32 system mail-user-agent is 'sendmail-user-agent. However when
> sending bug reports `mailclient-send-it' is used to send the message.
>
> You said you know how to fix it. Do you mean you have a solution for
> how to fix this bug in Emacs? 

Sorry, what i meant is that it was easy to fix *my* Emacs after I found
out what the problem was.
(Continue reading)

Permalink | Reply | 2 comments |

Gmane