From: "Ludwig, Mark" <ludwig.mark@siemens.com>
To: MBR <mbr@arlsoft.com>, "B. T. Raven" <nihil@nihilo.net>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: Why do replace commands sometimes not work?
Date: Fri, 25 May 2012 12:25:15 +0000 [thread overview]
Message-ID: <BC5672F8AD4C054BAF167C9801500D1A8BDB6C5A@USSLMMBX003.net.plm.eds.com> (raw)
In-Reply-To: <4FBEF607.8060209@arlsoft.com>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
I assume something like Valgrind has been applied to Emacs ... and it's clean.
Cheers,
Mark
From: help-gnu-emacs-bounces+ludwig.mark=siemens.com@gnu.org [mailto:help-gnu-emacs-bounces+ludwig.mark=siemens.com@gnu.org] On Behalf Of MBR
Sent: Thursday, May 24, 2012 10:01 PM
To: B. T. Raven
Cc: help-gnu-emacs@gnu.org
Subject: Re: Why do replace commands sometimes not work?
On 5/24/2012 10:41 PM, B. T. Raven wrote:
I can't reproduce that misbehavior on w32 ver 23.1
Both in *scratch* (lisp mode) and a junk file in text mode I get:
John Jacob Jingleheimerschmidt
" John Jacob Jingleheimerschmidt"
" John Jacob Jingleheimerschmidt"
John Jacob Jingleheimerschmidt
John Jacob Jingleheimerschmidt
where the second and third lines were originally camel-case in quotes.
I did assign the macro to a keychord with C-xC-kb
Ed
I'm not surprised that you can't reproduce it. It's so unpredictable that it reminds me of an assembly language bug I diagnosed many years ago where the code turned out to be making a critical decision based on data it fetched from an uninitialized memory location. In the case of this bug, the state of memory could depend on every keystroke I've typed since I started Emacs, the contents of every file it's opened, etc.
The example I gave was to illustrate the sort of problem I'm running into, to see if anyone else has encountered the same problem. I'd be thrilled if I could come up with a reproducible example, but I've had no luck on that front so far.
Mark
[-- Attachment #2: Type: text/html, Size: 5319 bytes --]
next prev parent reply other threads:[~2012-05-25 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1636.1337901354.855.help-gnu-emacs@gnu.org>
[not found] ` <5O-dnbLCNdm5bCPSnZ2dnUVZ5rmdnZ2d@giganews.com>
2012-05-25 3:01 ` Why do replace commands sometimes not work? MBR
2012-05-25 12:25 ` Ludwig, Mark [this message]
2012-05-25 3:19 ` Can't respond to B. T. Raven <nihil@nihilo.net> MBR
2012-05-25 9:03 ` Peter Dyballa
[not found] ` <mailman.1656.1337936620.855.help-gnu-emacs@gnu.org>
2012-05-25 12:52 ` B. T. Raven
2012-05-25 15:36 ` Why do replace commands sometimes not work? Barry Margolin
2012-05-24 23:15 MBR
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BC5672F8AD4C054BAF167C9801500D1A8BDB6C5A@USSLMMBX003.net.plm.eds.com \
--to=ludwig.mark@siemens.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbr@arlsoft.com \
--cc=nihil@nihilo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).