I'm new to joe 3.3, so far I've been using 3.1.
When more files are open and I want to move a text block from one file to
another, I get a "Modify other window first" if the file where the
highlightex text resides is not yet modified.
What's the purpose of this new behavior? This is very irritating to me. I
see no reason for it, while it makes my life more difficult.
If I realize that I didn't want to change the file where I copied the text
from (for example I pressed ^K M to move the block while in fact I wanted to
press ^K C to copy it), I can still do an undo in that buffer or I can close
that with losing the changes (^C). I've already done this in old joe dozens
of times. So I don't see my data is in risk due to such a wrong keypress.
On the other hand, this new behavior makes it harder if I want to modify
both files: move a certain part of text from one to the other.
So I'd like to request to revert the old simplest behavior.
From: Moritz Barsnick <barsnick@gm...> - 2005-06-07 12:50:59
Hi Egmont, hi list,
On Tue, Jun 07, 2005 at 14:09:38 +0200, Egmont Koblinger wrote:
> When more files are open and I want to move a text block from one file to
> another, I get a "Modify other window first" if the file where the
> highlightex text resides is not yet modified.
> What's the purpose of this new behavior? This is very irritating to me. I
> see no reason for it, while it makes my life more difficult.
IMHO, it's a bug.
I often get this: I want to copy more or less large blocks from one
file to another. I have both open side by side. I mark the block in
file A, switch to file B in the next window (^K^N), and try to copy
(^K^C). The marking of the block has then disappeared and the action
says: "No block". If I copy two smaller blocks of the same text
instead, it works.
I just can't reproduce consistently. I think I have also seen your
Get latest updates about Open Source Projects, Conferences and News.