Re: problem with zmacs regions

Don Cohen writes: > I notice this problem in xemacs 21.4 patch 22 running in linux in -nw > mode. It does not happen in xemacs 21.4 patch 8 (also linux, nw). > I mark a region and then try some command like untabify or sort lines > and get a complaint that the region is not active. First, tell us, are these built by you from source, or are they packaged from a Linux distribution? Next, try to reproduce the problem with xemacs -nw -vanilla. (If it doesn't, it's not really our problem -- we can't fix it -- but we'll try to help find workarounds and suggest fixes.) If at all possible find a reliable recipe. If xemacs -nw -vanilla does not produce the problem, we'll need to know what the contents of your custom and init files are, as well as the "default" and "site-start" libraries. For example, in XEmacs 21.4.22 on Macintosh I cannot reproduce with "xemacs -nw -vanilla" followed immediately by C-x h M-x sort-lines RET. How do you mark the region? Ie, do you use the mouse with GPM, C-SPC, Shift-arrowkey, or one of the mark-OBJECT commands such as mark-buffer == C-x h? Does it matter how you mark the region? Is the region visibly active (ie, highlighted)? Does it matter what mode(s) you are using? > Perhaps I did something to enter this weird state? Given that simply setting and resetting zmacs-regions seems to help, that's our first guess, but XEmacs should not surprise you this way. If it's a side effect of something you did, that should either be better documented or perhaps the side effect can be eliminated. > I wonder what. And how I can tell. If you notice an error that might be a bug, immediately doing C-h l will give you your most recent hundred or so keystrokes as well as the contents of the " *Message Log*" buffer. That will tell you what you've done recently.