bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Kill ring leak in winemacs macros


From: Peterson, Eric
Subject: Kill ring leak in winemacs macros
Date: Wed, 3 Aug 2005 09:01:18 -0400

To: address@hidden

Subject: Kill ring leak in winemacs macros

--text follows this line--

This bug report will be sent to the Free Software Foundation,

not to your local site managers!

Please write in English, because the Emacs maintainers do not have

translators to read other languages for them.

 

Your bug report will be posted to the address@hidden mailing list,

and to the gnu.emacs.bug news group.

 

In GNU Emacs 21.3.1 (i386-mingw-nt5.1.2600)

 of 2004-03-10 on NYAUMO

configured using `configure --with-gcc (3.2)'

Important settings:

  value of $LC_ALL: nil

  value of $LC_COLLATE: nil

  value of $LC_CTYPE: nil

  value of $LC_MESSAGES: nil

  value of $LC_MONETARY: nil

  value of $LC_NUMERIC: nil

  value of $LC_TIME: nil

  value of $LANG: ENU

  locale-coding-system: iso-latin-1

  default-enable-multibyte-characters: t

 

Please describe exactly what actions triggered the bug

and the precise symptoms of the bug:

 

When I create a keyboard macro in which I kill and yank form the EMACS kill ring and infinitely apply the macro via the "0" prefix argument, I have to make sure and not copy or kill into the Windows kill ring while the macro is running.  Otherwise this inadvertently introduces unwanted/unexpected data into the EMACS kill ring.  My macros can run for a long time on large files, so this can stop me from doing other work while I am waiting.  Or I can forget about the danger and corrupt the data I am manipulating.

 

A related issue is that EMACS macro's, I believe, used to run keyboard macros a *Lot* faster back in my Unix days in EMACS.  I quite suspect that the overhead of keeping the Windows kill ring consistant with the emacs kill ring is bogging the process down.

 

I couldn't find a version of or argument for EMACS "kill-line" or "kill-ring-save" that would help me.  I'm hoping for a solution that wouldn't require me to code and manipulation of "interprogram-cut-function" seemed to require codeing.

 

Anyway, thanks for the EMACS support!!!

 

-Eric

 

Recent input:

C-n C-n C-n C-n C-n C-x o C-a C-f C-f C-f w : C-a C-k

C-k C-y C-y C-p C-f C-f C-f C-f C-f C-f C-f C-b C-b

C-b C-b C-x o C-v C-x o / C-f C-f C-f C-f C-f C-f C-k

> C-h n <lwindow> <help-echo> <mouse-1> <mouse-1> <mouse-1>

<mouse-1> <mouse-1> <mouse-1> <mouse-1> <mouse-1> <mouse-1>

<mouse-1> <mouse-1> C-h a b u g <return> C-s C-g C-x

o C-s r e p o r t C-s C-s C-s C-n C-s C-s C-g C-x o

ESC x r e p o r t SPC e m SPC b SPC <return>

 

Recent messages:

Auto-saving...done

Loading outline...

Loading easy-mmode...done

Loading outline...done

Loading apropos...done

Type C-x 4 b RET to restore the other window.  C-M-v to scroll the help.

isearch-abort: Quit

Mark saved where search started

isearch-abort: Quit

Loading emacsbug...done<


reply via email to

[Prev in Thread] Current Thread [Next in Thread]