From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Gord Wait Newsgroups: gmane.emacs.bugs Subject: bug#7046: More info Date: Fri, 17 Sep 2010 11:45:36 -0700 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1284752912 21669 80.91.229.12 (17 Sep 2010 19:48:32 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 17 Sep 2010 19:48:32 +0000 (UTC) Cc: "'7046@debbugs.gnu.org'" <7046@debbugs.gnu.org> To: 'Stefan Monnier' Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Sep 17 21:48:29 2010 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OwgqH-00017u-JO for geb-bug-gnu-emacs@m.gmane.org; Fri, 17 Sep 2010 21:48:25 +0200 Original-Received: from localhost ([127.0.0.1]:56289 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Owgq5-0003jg-Ux for geb-bug-gnu-emacs@m.gmane.org; Fri, 17 Sep 2010 15:43:17 -0400 Original-Received: from [140.186.70.92] (port=33063 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Owgow-0003Eb-Cv for bug-gnu-emacs@gnu.org; Fri, 17 Sep 2010 15:43:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Owgna-0002Is-IU for bug-gnu-emacs@gnu.org; Fri, 17 Sep 2010 15:40:43 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:55328) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Owgna-0002Io-Er for bug-gnu-emacs@gnu.org; Fri, 17 Sep 2010 15:40:42 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1OwgIx-0005NJ-47; Fri, 17 Sep 2010 15:09:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gord Wait Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 17 Sep 2010 19:09:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 7046 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 7046-submit@debbugs.gnu.org id=B7046.128475050720644 (code B ref 7046); Fri, 17 Sep 2010 19:09:03 +0000 Original-Received: (at 7046) by debbugs.gnu.org; 17 Sep 2010 19:08:27 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OwgIM-0005Mt-5C for submit@debbugs.gnu.org; Fri, 17 Sep 2010 15:08:26 -0400 Original-Received: from mailex.lighthauslogic.com ([207.216.240.196]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Owfwy-0005EK-R6 for 7046@debbugs.gnu.org; Fri, 17 Sep 2010 14:46:21 -0400 Original-Received: from tweety.yvr.lighthauslogic.com ([192.168.2.12]) by tweety.yvr.lighthauslogic.com ([192.168.2.12]) with mapi; Fri, 17 Sep 2010 11:48:43 -0700 Thread-Topic: bug#7046: More info Thread-Index: ActWffpsWYYx6m1MSKeAyXENi4BC1wAGhVGw In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mailman-Approved-At: Fri, 17 Sep 2010 15:08:23 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Fri, 17 Sep 2010 15:09:03 -0400 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:40268 Archived-At: Hopefully this update will make it, Glenn Morris emailed me to note that th= e 7046 bug got closed (by accident).. Here is the explanation. Below it are some sample lines. Build a file with = a couple hundred of those lines to test against.. -------------------------------------------- The goal of the edit work is to cut the last "word" of each line and place = it as the first "word" of each line. (Later I sort-lines, this way the lines are sorted by the value of the orig= inal last word of the line).. I create a keyboard macro that knows the line syntax, and does one line of = work: (fset 'moveword [?\C-s ?- ?t ?o ?\C-f ?\C- ?\C-e ?\C-w ?\C-a ?\C-y ? ?\C-a ?\C-n]) Macro edit view of the same thing: Macro: C-s ;; isearch-forward -to ;; self-insert-command * 3 C-f ;; forward-char C-SPC ;; set-mark-command C-e ;; move-end-of-line C-w ;; kill-region C-a ;; move-beginning-of-line C-y ;; yank SPC ;; self-insert-command C-a ;; move-beginning-of-line C-n ;; next-line Place the cursor at the start of any line and run the macro once (Esc-x moveword) It finds the ascii "-to" word, moves ahead to the last word, cuts and paste= s it at the start, then drops down one line. Try it repeatedly for a few lines manually to show the macro works as desir= ed.. Now try to auto repeat the macro 100 times: (Ctrl-u 100 Esc-x moveword) Macro repeats, but at some point starts skipping a line. I also manually executed the macro succesfully on lines that failed the 100= repeat, to show that it wasn't some artifact of those failed lines.. ----------------------------------------------- Sample lines to be manipulated by the macro.. Make a file with a few hundre= d of these in it. Duplicating these ones will be fine to show the bug. In t= he real file each line is unique. ----------------------------------------------- set_location_assignment PIN_AP23 -to ddr3bot_dq[36] set_location_assignment PIN_AM23 -to ddr3bot_dq[35] set_location_assignment PIN_AT23 -to ddr3bot_dq[34] set_location_assignment PIN_AN23 -to ddr3bot_dq[33] set_location_assignment PIN_AU23 -to ddr3bot_dq[32] set_location_assignment PIN_AK17 -to ddr3bot_dq[31] set_location_assignment PIN_AG17 -to ddr3bot_dq[30] set_location_assignment PIN_AH17 -to ddr3bot_dq[29] set_location_assignment PIN_AG16 -to ddr3bot_dq[28] set_location_assignment PIN_AL17 -to ddr3bot_dq[27] set_location_assignment PIN_AH16 -to ddr3bot_dq[26] set_location_assignment PIN_AM17 -to ddr3bot_dq[25] set_location_assignment PIN_AJ16 -to ddr3bot_dq[24] set_location_assignment PIN_AU15 -to ddr3bot_dq[23] set_location_assignment PIN_AR17 -to ddr3bot_dq[22] set_location_assignment PIN_AT15 -to ddr3bot_dq[21] set_location_assignment PIN_AP17 -to ddr3bot_dq[20] set_location_assignment PIN_AV16 -to ddr3bot_dq[19] set_location_assignment PIN_AN16 -to ddr3bot_dq[18] set_location_assignment PIN_AW16 -to ddr3bot_dq[17] set_location_assignment PIN_AT16 -to ddr3bot_dq[16] set_location_assignment PIN_AW12 -to ddr3bot_dq[15] set_location_assignment PIN_AV11 -to ddr3bot_dq[14] set_location_assignment PIN_AU14 -to ddr3bot_dq[13] set_location_assignment PIN_AW11 -to ddr3bot_dq[12] set_location_assignment PIN_AV14 -to ddr3bot_dq[11] set_location_assignment PIN_AU12 -to ddr3bot_dq[10] set_location_assignment PIN_AW14 -to ddr3bot_dq[9] set_location_assignment PIN_AT12 -to ddr3bot_dq[8] set_location_assignment PIN_AP13 -to ddr3bot_dq[7] set_location_assignment PIN_AP14 -to ddr3bot_dq[6] set_location_assignment PIN_AN13 -to ddr3bot_dq[5] set_location_assignment PIN_AR14 -to ddr3bot_dq[4] set_location_assignment PIN_AL14 -to ddr3bot_dq[3] set_location_assignment PIN_AN14 -to ddr3bot_dq[2] set_location_assignment PIN_AM13 -to ddr3bot_dq[1] set_location_assignment PIN_AM14 -to ddr3bot_dq[0] set_location_assignment PIN_AL23 -to ddr3bot_dqs_n[7] set_location_assignment PIN_AU26 -to ddr3bot_dqs_n[6] -----Original Message----- From: Stefan Monnier [mailto:monnier@IRO.UMontreal.CA] Sent: Friday, September 17, 2010 8:35 AM To: Gord Wait Cc: '7046@debbugs.gnu.org' Subject: Re: bug#7046: More info > I also tried using "forward-line" and got similar results. It seems > to be dependent on how many repeats I select. If I auto repeat say 10 > lines worth, It seems to be ok. If I auto repeat the macro 1000 times, > then it starts to skip every line at some point.. Both cases sound like bugs, but without a concrete test case it's difficult to track it down. Can you provide a precise test case (e.g. a sample file and the key strokes you hit to define and run the macro, ideally starting from "emacs -Q")? Stefan This e-mail may contain information that is privileged, confidential or oth= erwise exempt from disclosure under applicable laws. Unauthorized use, repr= oduction or dissemination of the e-mail is strictly prohibited. If you have= received this e-mail in error, please contact the sender immediately. [11E= ABB509DF]