Ar an ceathrú lá déag de mí na Nollaig, scríobh Sean MacLennan:
> [...] For example, `describe-function lisp-mode' points you at the source
> in /usr/share/emacs. For all the XEmacs versions I have used it points
> you at a bogus build dir. Even on the machines where I built XEmacs the
> path is wrong.
Right now, that actually works fine for me. F1 f lisp-mode gives source-lisp
when it’s readable:
`lisp-mode' is an interactive built-in compiled Lisp function
-- loaded from "/home/aidan/xemacs-21.5-car-safe/lisp/lisp-mode.elc"
And then lisp-directory if source-lisp isn’t readable:
`lisp-mode' is an interactive built-in compiled Lisp function
-- loaded from "/home/aidan/share/xemacs-21.5-b34/lisp/lisp-mode.elc"
(lisp-mode)
Are things different for you with 21.5-b34?
--
‘Liston operated so fast that he once accidentally amputated an assistant’s
fingers along with a patient’s leg, […] The patient and the assistant both
died of sepsis, and a spectator reportedly died of shock, resulting in the
only known procedure with a 300% mortality.’ (Atul Gawande, NEJM, 2012)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
When I tried to push my xemacs-gtk changes into xemacs/xemacs-gtk, I got
the following error:
[jsparkes src]$ hg push xemacs-gtk
pushing to https://bitbucket.org/xemacs/xemacs-gtk
searching for changes
abort: empty or missing revlog for lock/.precious
[jsparkes src]$
lock/.precious is a file apparently left over from CVS. I had deleted it
quite a while ago.
Following the advice in
http://mercurial.selenic.com/wiki/RepositoryCorruption, I ran a verify:
[jsparkes src]$ hg verify
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
data/lock/.precious.i@104: missing revlog!
104: empty or missing lock/.precious
lock/.precious@104: 692a62877542 in manifests not found
5120 files, 6324 changesets, 51125 total revisions
3 integrity errors encountered!
(first damaged changeset appears to be 104)
I fixed this using the procedure in section 4.3.
(I just wanted this on the record in case it causes problems in the future.)
--
Jeff Sparkes
jsparkes(a)gmail.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
I am using Didier Verna's rcfiles package (thanks Didier!). But I found
that I couldn't get it to work with some packages such as lisp-mode.
The rcfiles package uses `eval-after-load' which looks up the mode in
`load-history' to see if it has already been loaded. If so, it runs the
form for you.
But, unfortunately, files such as lisp-mode have the full path rather
than a simple load name. This path is useless on any machine except the
build machine.
So I wrote some simple code to massage the load-history so it would
work.
(setq load-history
(mapcar (lambda (elt)
(let ((a (car elt)))
(if (eq 0 (string-match "/.*/\\([^/]+\\)\.elc" a))
(list (match-string 1 a) (cdr elt))
elt)))
load-history))
Feel free to make fun of the code.... or make suggestions.... but my
real question is: will this cause problems? Anybody know of code that
needs the full path?
Cheers,
Sean
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
>>>>> Didier Verna <didier(a)xemacs.org> writes:
> Only bad ones, if any :-)
OK. Since there were no good ones I updated the Makefile and pushed it
so it is easier to use rcfiles.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi
I had a similar question a couple of weeks ago, concerning hyper, but
this one is more important.
I have to use an old Laptop which does not have a WIN key, which I
usually map to super (and use frequently)
Now I thought of doing two things, since I never use capslock:
- switch capslock and control.
- map capslock to super.
The xmodmap code for swapping control and capslock is:
remove Lock = Caps_Lock
remove Control = Control_L
keysym Control_L = Caps_Lock
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L
The code of mapping Capslock (not swapped) to super is.
remove Lock = Caps_Lock
keysym Caps_Lock = Super_L
add Mod4 = Super_L
Both work, so I want to combine them using
remove Lock = Caps_Lock
remove Control = Control_L
keysym Control_L = Super_L
keysym Caps_Lock = Control_L
add Mod4 = Super_L
add Lock = Caps_Lock
But super is mapped correctly but control now is no longer there
Anybody has an idea?
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Let's get some more opinions. Moving to xemacs-beta from xemacs-patches.
Michael Sperber writes:
> "Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
> > Michael Sperber writes:
> > > * simple-more.el:
> > Isn't there a better place in xemacs-base for these (I grant that
> > they're commonly-enough used that fsf-compat is wrong)? Hm. Maybe not.
>
> :-) I'm open for suggestions.
We surely don't need both "simple-more.el" and "subr-more.el". (In
fact, I mistook one for the other already. I prefer the name
"simple-more"; I can't see any reason why the functions currently in
subr-more.el would ever be considered "primitives." But that would be
more work for you (or whoever adds the simple-more functions) since I
think at least one package already requires simple-subr.
BTW, subr-more.el sucks. The docstring of `number-sequence' displays
a complete misunderstanding of floating point arithmetic. (Floating
point *arithmetic* is *not* "inexact"; it's that many numbers that can
be exactly represented with decimal numerals cannot be exactly
*represented* as binary floating point numbers in the computer).
`string-match-p' uses `match-data' and `store-match-data' rather than
`save-match-data' (may be safer since it uses an unwind-protect).
`add-to-history' is broken, it uses delete on a list without a set.
N.B. The relevant sexp in our `read-from-minibuffer' does it right.
I'm also not sure I agree with `add-to-history's logic, but it's not
too bad, and I think I know how to improve it bug-compatibly.
I'll try to get around to fixing and pushing by the weekend, but no
promises.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Dear developer,
The recent added ido mode have a annoying bug when one try to find-file
from history filenames.
To reproduce:
Prepare a ido history by following steps.
==============================
1. make following directory structure
~/workspace/foo/
~/workspace/foo/kakabaa.txt
~/workspace/foo/kakafoo.txt
2. run xemacs
3. enable ido-mode
4. open file ~/workspace/foo/kakabaa.txt
5. kill buffer and exit xemacs
steps to reproduce:
===============
1. run xemacs
2. make sure the pwd is not ~/workspace/foo/
3. enable iso-mode if it was not enabled by default.
4. C-x C-f kaka and wait for a second so that ido-mode will search the file
history to provide a list of file to complete.
expected result
============
ido-mode should provide a suggestion in minibuffer looks like with point at
<P>:
(Find File): ~/workspace/foo/kaka<P>[baa.txt] [foo.txt]
This way, it allows me to to narraw down the suggested list by type a
additional letter "b" or "f".
minibuffer with issue
================
ido-mode provided suggestion in minibuffer looks like with point at <P>:
(Find File): ~/workspace/foo/<P>kaka[baa.txt] [foo.txt]
As we can see that if I type a additional letter "b" or "f", I will get a
wrong filename bkaka or fkaka.
Thanks,
Kai
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Just noticed that when I use tramp and enter a tramp pathname using
ssh, I get an error that subr-more was not loaded.
If I manually do M-x load-lib subr-more and then use tramp, everything
works.
This is something "recent". I haven't used tramp in a while, but I
didn't have this problem sometime ago.
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
The redraw issues that I have seen have been caused by the "widgets"
support in XEmacs. I haven't got that totally working. Compiling without
the widgets avoids a bunch of redisplay issues. The only thing you will
notice is that buffer tabs are missing, but they can cause a redisplay
loop, so you're better off.
Should I turn this off in configure.ac?
--
Jeff Sparkes
jsparkes(a)gmail.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta