5:18 p.m.
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.
Judging by the
(setf zmacs-regions nil) solves the problem.
Interestingly, setting it back to t then leaves me in a state where
the problem does not occur.
Perhaps I did something to enter this weird state?
I wonder what. And how I can tell.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:36 a.m.
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.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
6:02 p.m.
Stephen J. Turnbull 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?
This machine runs CentOS release 5.4
According to my notes there was no yum package available and I ended
up doing this:
2010-02-13
wget ftp.xemacs.org/pub/xemacs/stable/xemacs-21.4.22.tar.gz
gzip -dc xemacs-21.4.22.tar.gz | tar xf -
cd xemacs-21.4.22
./configure
make install
wget ftp.xemacs.org/pub/xemacs/packages/xemacs-mule-sumo.tar.gz
mv xemacs-mule-sumo.tar.gz /root/
cd /usr/local/lib/xemacs/
gunzip /root/xemacs-mule-sumo.tar.gz
tar xf /root/xemacs-mule-sumo.tar
cd
wget ftp.xemacs.org/pub/xemacs/packages/xemacs-all-packages.tar.gz
gunzip xemacs-all-packages.tar.gz
cd /usr/local/lib/xemacs/
tar xf /root/xemacs-all-packages.tar
I started a new terminal, ran xemacs -nw again and did not see the
same behavior. So I must have done something to put it into this
strange mode. But I can't figure out what.
The interesting thing I saw was that after marking the region I would
see the region highlighted, and then I'd type m-x and after typing
one more character, the s for sort lines or the u for untabify, the
highlighting would disappear. Is that a useful hint?
As it turns out, this is the first time I've seen this particular
problem, but there's another one that I've seen a lot and I'd be even
more interested in finding out how to fix. This one happens on many
different machines. Again I don't know how I get into this mode.
I'm in a dired buffer.
I type f to go to a buffer.
I see in the minibuffer "Failing I-search backward: f".
I type c-g and get a backtrace buffer:
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
isearch-top-state()
isearch-pop-state()
#<compiled-function nil "...(33)" [isearch-invalid-regexp isearch-opoint
isea$
call-interactively(isearch-abort)
As long as I leave that backtrace buffer I can then go back to the
dired and type f and get to the buffer. When I type q to get out of
the backtrace I'm back in the same state.
Also in that state I seem to be in the middle of a search, so that
when I type c-s it's as if I've already typed a bunch of text.
How do you mark the region?
I only know one way to do it, which
is c-space and then move.
This is in an xterm where I've run ssh to talk to another machine and
inside that ssh I've done xemacs -nw.
Given that simply setting and resetting zmacs-regions seems to help,
What should/could be different between the original state and the
result of setting and resetting zmacs-regions?
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.
I've actually increased the number stored to 10000 in
most of my
xemacs's. That affects (recent-keys ) though help - l still only
shows 100.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:01 a.m.
On Tue, Oct 26, 2010 at 11:02 AM, Don Cohen
<don-temp288(a)isis.cs3-inc.com> wrote:
This machine runs CentOS release 5.4
According to my notes there was no yum package available and I ended
up doing this:
If you are able to use the EPEL repository, there's an xemacs-21.5.29
package in there. I might admit, under duress, that I had something
to do with its creation. (I am not the current maintainer of it, but
it's close enough to the Fedora version, which I do maintain, that I
can probably answer questions about it.)
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
6 p.m.
Am 26.10.2010 05:36, schrieb Stephen J. Turnbull:
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.
Hi,
when reading the code several month ago, got the impression there are
circulars and redundant things in it.
Andreas
--
https://code.launchpad.net/~a-roehler/python-mode/python-mode-components
https://code.launchpad.net/s-x-emacs-werkstatt/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4921
days inactive
4926
days old
4 comments
4 participants
participants (4)
-
Andreas Röhler -
Don Cohen -
Jerry James -
Stephen J. Turnbull