From: Mike Baranski <mike@spamoff.nospam.remove.secmgmt.com>
Subject: Bug in remote file save.
Date: Thu, 12 Sep 2002 09:12:56 -0400 [thread overview]
Message-ID: <3d80920b$0$306$39cecf19@nnrp1.twtelecom.net> (raw)
Couldn't send this via email, so here it is:
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 bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.
In GNU Emacs 21.2.1 (i386-redhat-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2002-04-08 on porky.devel.redhat.com
configured using `configure i386-redhat-linux --prefix=/usr
--exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib
--libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com
--mandir=/usr/share/man --infodir=/usr/share/info --with-gcc --with-pop
--with-sound'
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: en_US
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:
I dired a directory remotely, C-xd /me@server:/var/www/html/website, open
and edit a file, it saves the first time correctly. For each further edit,
it gives a beep and the message "Keyboard macro terminated by command
ringing the bell". Then, emacs thinks that I have an old copy of the file,
and gives the messages confirming that I want to edit an old version, and
prompting the next time I save to verify that I want to overwrite a newer
file. When the beep comes, the file is not saved properly.
Recent input:
f t p SPC b r o k e n <return> w h e n SPC I SPC <backspace>
<backspace> <backspace> <backspace> <S-backspace> <S-backspace>
<S-backspace> W h e n SPC I SPC p o <backspace> <backspace>
o p e n SPC a SPC r e m o v <backspace> t e SPC f i
l e , SPC <escape> k <escape> k <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> f <return> <backspace> C-x C-s
<return> <return> <backspace> <backspace> C-x C-s <escape>
x r e p o r t - e m <tab> <return>
Recent messages:
Getting PWD...done
Listing /mike@wsc:/var/www/html/olema/...done
Retrieving c_law.php...done
syntax: ((topmost-intro . 1)), indent: 0
Loading time-stamp...done
Writing c_law.php...done
Wrote c_law.php
syntax: ((topmost-intro . 1)), indent: 0 [2 times]
backward-delete-char-untabify: Beginning of buffer
c_law.php changed on disk; really edit the buffer? (y, n, r or C-h)
byte-code: Keyboard macro terminated by a command ringing the bell
reply other threads:[~2002-09-12 13:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='3d80920b$0$306$39cecf19@nnrp1.twtelecom.net' \
--to=mike@spamoff.nospam.remove.secmgmt.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).