[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem report #61
From: |
Stuart D. Herring |
Subject: |
Re: Problem report #61 |
Date: |
Tue, 11 Apr 2006 11:08:54 -0700 (PDT) |
User-agent: |
SquirrelMail/1.4.3a-11.EL3 |
> At conditional (17): "current_buffer == prev_buffer" taking true path
> At conditional (18): "last_point_position != ((current_buffer)->pt + 0)"
> taking true path
> At conditional (19): "Vdisable_point_adjustment == Qnil" taking true path
> At conditional (20): "Vglobal_disable_point_adjustment == Qnil" taking
> true path
> At conditional (21): "already_adjusted == 0" taking true path
>
> 1870 if (current_buffer == prev_buffer
> 1871 && last_point_position != PT
> 1872 && NILP (Vdisable_point_adjustment)
> 1873 && NILP (Vglobal_disable_point_adjustment)
> 1874 && !already_adjusted)
>
> Event uninit_use: Using uninitialized value "prev_modiff"
> Also see events: [var_decl]
>
> 1875 adjust_point_for_property (last_point_position, MODIFF !=
> prev_modiff);
> 1876
This can only happen if last_point_position at entry to command_loop_1
isn't equal to (point) at this point (ha) and read_key_sequence returns -1
the first time through the loop (before already_adjusted is set). Maybe
some nasty filter or timer could cause this? If so, should probably start
with already_adjusted set to 1 so as to avoid random extra adjusts. If
not, no bug.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
- Problem report #61, Dan Nicolaescu, 2006/04/11
- Re: Problem report #61,
Stuart D. Herring <=