From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8bc34e14e4555720 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-20 02:29:40 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!btnet-peer1!btnet-peer0!btnet!news5-gui.server.ntli.net!ntli.net!news6-win.server.ntlworld.com.POSTED!not-for-mail Sender: mjw@golux Newsgroups: comp.lang.ada Subject: Re: This is a simple question References: <9pk4t7$tbm$1@trog.dera.gov.uk> <87zo762rta.fsf@deneb.enyo.de> <9pkc0r$m5j$1@trog.dera.gov.uk> <9pkddm$afh$1@nh.pace.co.uk> <9pvdp5$8im$1@nh.pace.co.uk> <3BC48598.80703@home.com> <87lmije4lt.fsf@deneb.enyo.de> <3BC5D230.6030702@home.com> <3BCB228E.1010700@home.com> <9qhsvv$e01$1@a1-hrz.uni-duisburg.de> <3BCDBC41.3070305@home.com> <3BCEFED0.2060302@home.com> <87y9m8ak7i.fsf@chiark.greenend.org.uk> <3BCF4115.7080809@home.com> From: Matthew Woodcraft Message-ID: <87ofn2ack8.fsf@chiark.greenend.org.uk> User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: 20 Oct 2001 10:24:55 +0100 NNTP-Posting-Host: 213.107.104.73 X-Complaints-To: abuse@ntlworld.com X-Trace: news6-win.server.ntlworld.com 1003569874 213.107.104.73 (Sat, 20 Oct 2001 10:24:34 BST) NNTP-Posting-Date: Sat, 20 Oct 2001 10:24:34 BST Organization: ntl Cablemodem News Service Xref: archiver1.google.com comp.lang.ada:14957 Date: 2001-10-20T10:24:55+01:00 List-Id: "Warren W. Gay VE3WWG" writes: > Matthew Woodcraft wrote: > > Indeed, this behaviour of repeat-on-final-keystroke after > > call-last-kbd-macro is clearly just an emacs bug. I have reported it to > > bug-gnu-emacs@gnu.org. > > -M- > Thank you. I really do look forward to switching to GNU emacs someday, > > but this "feature" is important to me. Is there an easy way/URL where I can > monitor the resolution of this "bug"? TIA. They don't seem to have a proper bug-tracking system. You can see the message in their mail archive at http://mail.gnu.org/pipermail/bug-gnu-emacs/2001-October/007167.html -M-