Are there any views on the future of Quail in XEmacs?
I've been going back to the problem of getting Quail working properly
in isearch. I'm almost there, but it is, if you'll excuse my French, a
total bloody nightmare. isearch-mode is a twisty self-connecting maze,
and so is Quail, so the combination is a 4D twisty multiply
self-connecting maze with singularities of of hideous complexity.
(The fact that XEmacs has three different definitions of what the
minibuffer is, doesn't help, and caused me much grief until I
understood it. And since they play fast and loose with events and
buffers, the Lisp debugger was pretty much useless.)
In FSFmacs, it works much more neatly, because there are a couple more
hooks into Quail. It also looks neater, because of a couple more
variables which were left out in XEmacs.
I have to change Quail anyway even to get my stuff working, so if I
were to bring in a few of the FSF changes, would you accept it into
the standard packages, along with an updated isearch-mode ?
(I usually work from the 21.4 codebase, but I guess there's no reason
why the mods in the 21.5 isearch-mode.el shouldn't go back into 21.4
too, if there's ever another release.)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Ar an séú lá déag de mí Feabhra, scríobh Mats Lidell:
> >>>>> Aidan Kehoe <kehoea(a)parhasard.net> writes:
>
> Aidan> Ar an séú lá déag de mí Feabhra, scríobh Mats Lidell:
>
> Aidan> Not in practice, none of the modules appear to use it. But if
> Aidan> people felt it appropriate to export acons(), then it's equally
> Aidan> appropriate to export Facons() to the modules. I've just
> Aidan> committed the below, thanks for the reports.
>
> No problem. I understood I was in deep water so I didn't want to
> submit my fix. ;-)
>
> I don't really understand how Facons can replace acons. Or was it that
> acons was the symbol to make external while it was implemented in lisp
> and Facons is the c-code symbol? So if a module now would like to use
> acons it should link, use, to the Facon symbol? Modules need to know
> if the function is implemented in C or in lisp?
In a way, yes. The internals manual says this (and this is actually the only
part of the internals manual relevant to this question):
‘All C functions that are Lisp primitives begin with a capital F, and no
others should begin this way.’
It’s not a big deal one way or the other, any call to acons (X, Y, Z) is
equivalent to Fcons (Fcons (X, Y), Z), and any incompatibility can be
eliminated by using the latter form.
> But I should very, very probably read some internals documents since I
> don't know a thing about how lisp interfaces to C in XEmacs. Is it
> RTFM again? ;-)
--
“Apart from the nine-banded armadillo, man is the only natural host of
Mycobacterium leprae, although it can be grown in the footpads of mice.”
-- Kumar & Clark, Clinical Medicine, summarising improbable leprosy research
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
>>>>> Jeff Sparkes <jsparkes(a)gmail.com> writes:
Jeff> Where is it getting acons from? It's not in the source any
Jeff> more, or in the object files.
It is in xemacs.def and used by dlltool to produce xemacs-export.o
which then contains an undefined reference to '_acons'
This was my next question. If Aidans patch simply made acons in C
visible instead of acons in lisp why do we get the undefined
reference?
Removing acons from xemacs.def fixes the undefined reference but it is
right, does it undermine anything for the modules?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
[ I think I sent this with some accidentally permuted From address -
sorry if this is the second. ]
Is there any thought on the future of Quail in XEmacs?
I went back to the problem of getting Quail working properly in
isearch, and I'm almost there, though it has been a nightmare, as
isearch is a twisty self-connected maze, and so is Quail, so the
combination is a twisty 4D multiply self-connected maze.
(It doesn't help that XEmacs has three different definitions of
minibuffer - I spent ages working out why my code did something
slightly odd! And the debugger doesn't seem usable with code that
plays fast and loose with events. Could it ever be?)
However, in FSFmacs it already works, and does so with less
contortions, owing to a few things in their Quail and isearch
that aren't in ours.
I had to modify quail anyway, so I wondered: if I were to bring some
of the FSF changes into quail and isearch, would you take them up? (I
usually work with the 21.4 codebase, but there are only minor changes
in isearch between 21.4 and 21.5.)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi,
The recent acons change breaks the cygwin build. acons is exported in
xemacs.def. Removing that from xemacs.def makes the build succeed.
But before doing that I must ask what is xemacs.def good for. A quick
check in the Makefiles reveals that dlltool is involved. The manpage
for dlltool talks about "Create files needed to build and use DLLs"
But I fail to find any DLLs being built!? Please enlighten me.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2011-02-08 - 2011-02-15)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
508 open ( +0) / 240 closed ( +0) / 748 total ( +0)
Open issues with patches: 11
Average duration of open issues: 786 days.
Median duration of open issues: 808 days.
Open Issues Breakdown
new 178 ( +0)
deferred 6 ( +0)
napping 4 ( +0)
verified 51 ( +0)
assigned 155 ( +0)
committed 25 ( +0)
documented 2 ( +0)
done/needs work 24 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
XEmacs 21.5 has next-single-char-property-change that behaves
differently from the version in emacs. When there is no
next-single-char-property-change, XEmacs returns nil. But Emacs
(according the docstring) returns the end of the object. Similarly,
previous-single-char-property-change has the same problem.
Is this difference intentional? FWIW, it breaks slime, which assumes
Emacs' behavior. For right now, I'm just doing
(or (next-single-char-property-change <args>) (point-max))
which works for slime.
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
On 2/11/2011 9:32 PM, Brian Palmer wrote:
> On Fri, Feb 11, 2011 at 6:14 PM, Eric S. Johansson <esj(a)harvee.org
> <mailto:esj@harvee.org>> wrote:
>
> Emacs uses #filename as the public name for locking a file. This is not
> working
> with vocola because it uses a very dumb match on ".Vcl". So, I would like to
> change the file name used for a lock file but I haven't found in the
> documentation yet. A pointer would be appreciated
>
>
> This is an "auto save file" ( see (xemacs)Auto Save Files). You can redefine
> make-auto-save-file-name with something like
lrwxrwxrwx 1 esj None 15 Feb 12 01:03 .#init.el -> esj(a)jumper.4332
Reading through the documentation, says that should have been #init.el#. Why the
difference?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi,
after upgrading to Debian squeeze and assuring to have again
XEmacs21-nomule I have a problem with bbdb: Reading any email I get the
error message "No such coding system utf-8" as bbdb is trying to encode
names with utf-8. (See trace below.)
Looking at bbdb.el I find:
(defun bbdb-name-normalize (name)
"Return normalized NAME.
NAME is converted to lower case and in a MULE enabled Emacs it is converted to
UTF-8 or unibyte to unify the overlapping ISO-8859-* encodings.
You may advice this function to allow more sophisticated normalizations."
(when name.
(setq name (downcase name))
(cond ((functionp 'encode-coding-string)
(funcall 'encode-coding-string name 'utf-8))
((functionp 'string-make-unibyte)
(funcall 'string-make-unibyte name))
(t
name))))
But this means that my XEmacs-nomule works like a MULE enabled Emacs!
As a workaround I changed that function, but the real solution would be
to get XEmacs-nomule not to "assume" to be MULE enabled! (As a matter of
fact, starting up XEmacs, I now always get the warning "X-Symbol: cannot
deduce default encoding, I'll assume `iso-8859-1'". I guess that's also
some MULE-related error message which in XEmacs-nomule doesn't make much
sense.)
I guess this is a bug, but I don't know on which level: Is a bbdb-bug
checking for mule by checking for the presence of
"encode-coding-string"? A debian bug, by making available
"encode-coding-string" in xemacs21-nomule? A xemacs-bug? Or whatever?
Thanks a lot in advance
Andreas Gösele
Debugger entered--Lisp error: (error "No such coding system" utf-8)
encode-coding-region(1 19 utf-8)
encode-coding-string("john doe" utf-8)
bbdb-name-normalize("John Doe")
bbdb-name=("John Doe" "John Doe")
bbdb-annotate-message-sender(("John Doe" "joh.doe(a)some.where") t prompt bbdb-prompt-for-create)
byte-code("..." [matches records record net rest-of-nets done annotating bbdb-annotate-message-sender t bbdb-prompt-for-create searching "^" regexp-quote "$" nil bbdb-search-invert-p 6 string-match "" q 0 5 format "Hit C-g to stop BBDB from %s. %d of %d addresses processed." featurep xemacs bbdb-display-message progress message sit-for processed-addresses bbdb-address bbdb-update-records-mode invert mess auto-create-p bbdb-offer-to-create bbdb-case-fold-search offer-to-create bbdb-records case-fold-search hits bbdb-silent-running bbdb-gag-messages addrslen] 7)
bbdb-update-records(((authors "From" ("John Doe" "joh.doe(a)some.where"))) prompt nil)
bbdb/gnus-update-records(nil)
bbdb/gnus-pop-up-bbdb-buffer()
run-hooks(bbdb/gnus-pop-up-bbdb-buffer)
apply(run-hooks bbdb/gnus-pop-up-bbdb-buffer)
gnus-run-hooks(gnus-article-prepare-hook)
gnus-article-prepare-display()
gnus-article-prepare(45574 nil)
gnus-summary-display-article(45574 nil)
gnus-summary-select-article(nil nil pseudo)
gnus-summary-scroll-up(1)
call-interactively(gnus-summary-scroll-up)
--
Omnis enim res, quae dando non deficit, dum habetur et non datur,
nondum habetur, quomodo habenda est.
Augustinus, De doctrina christiana
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta