On 01/27/2010 03:09 AM, Bernhard Herzog wrote:
On 27.01.2010, Jeff Bauer wrote:
It used to be if my cursor was positioned on
(0,1) and I pressed ^N, the cursor would jump
down to the second line of code (0,3). Now it
goes to (0,2) which is still considered (0,50).
That's a new default in Emac
On Jan 27, 2010, at 4:09 AM, Bernhard Herzog wrote:
> That's a new default in Emacs 23 called visual line mode IIRC.
> You can get the old behavior back with the following setting in ~/.emacs:
>
> (setq line-move-visual nil)
Yep, this one annoyed the crap out of me too when I upgraded, until I f
On 27.01.2010, Jeff Bauer wrote:
> After upgrading to emac23, I noticed one big
> difference in editing python code ... or, well
> editing anything.
>
> 0123456789012345678901234567890123456789
>1 One-really-long-line-of-text-and-newline
>2 -doesn't-appear-until-full-stop-HERE.
>
Jeff Bauer wrote:
> After upgrading to emac23, I noticed one big
> difference in editing python code ... or, well
> editing anything.
>
> 0123456789012345678901234567890123456789
> 1 One-really-long-line-of-text-and-newline
> 2 -doesn't-appear-until-full-stop-HERE.
> 3 Second-line-of
After upgrading to emac23, I noticed one big
difference in editing python code ... or, well
editing anything.
0123456789012345678901234567890123456789
1 One-really-long-line-of-text-and-newline
2 -doesn't-appear-until-full-stop-HERE.
3 Second-line-of-code
It used to be if my cursor