11:21 a.m.
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Uwe Brauer writes:
> >>>>> "Aidan" == Aidan Kehoe <kehoea(a)parhasard.net>
writes:
>
> >>
> >> Which is find surprising. Can somebody please clarify me that
> >> issue.
>
> > This is a bug that was mostly eliminated in 21.5 with a sync
> > from the FSF back in 2005. See
> > http://mid.gmane.org/84k6q0ikcn.fsf＠xemacs.org .
>
> And what about the poor 21.4 users they have to live with that
> bug?
Why don't you try to apply that patch to 21.4? If it works,
report it
and we'll give it a try.
The point is I am on (K)ubuntu and I want to use their xemacs and not
to build me own, especially since they managed to have mule/nomule and
the same time. But on they other hand this is feature I need quite a
bit so I might test it. May be I do that, and then try to convince Vin
and the debian manager to apply it.
Also, if you want something done in 21.4, it can't hurt to
gently
lobby Vin Shelton <acs(a)xemacs.org>, whose approval is required to
apply the patch and release a new XEmacs in any case.
Vin, has anybody tested that patch in 21.4, and if so
are you willing to apply it?
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
7:28 p.m.
New subject: indent-new-comment-line misbehaviour?
First things first. A patch to 21.5 may fail to apply to 21.4, but
you can probably get a copy of 21.5 version of that function from
http://hg.debian.org/hg/xemacs/xemacs, and put the defun in init.el,
where it will override the built-in.
Second, I see that this comes from something called "newcomment.el",
so it may not work at all without the rest of the new comment stuff.
You may copy that whole file to ~/.xemacs and put
(load (expand-file-name "~/.xemacs/newcomment.elc"))
in init.el after you've tested a bit by loading by hand (and the very
first time you want to do M-x byte-compile-and-load-file on it).
Uwe Brauer writes:
The point is I am on (K)ubuntu and I want to use their xemacs and
not
to build me own, especially since they managed to have mule/nomule and
the same time.
Yes, we understand that. But this is part of the XEmacs core, so
(1) You need to wait for the Ubuntu process to pick up the next
release of XEmacs 21.4. We have zero control over that.
(2) They need to wait for us to release. Only Vin has much say in
that. He has been relatively actively posting recently, but he
doesn't post a schedule since XEmacs 21.4 is relatively bug-free
and releases are done as patches accumulate.
(3) The bug report and patch we have is obscure and old.
All of the above lower each individual developer's incentive to do
anything about it in advance of word from Vin. He on the other hand
doesn't have an easy way to track old patches. So you end up with a
de facto low priority on this kind of request.
All that also means that you're going to have quite a wait for an
Ubuntu version with the patch in it.
It's entirely your choice; I'm telling you what you can do to bump
your priority and speed up the process.
But on they other hand this is feature I need quite a bit so I
might test it. May be I do that, and then try to convince Vin and
the debian manager to apply it.
Your testing will make a big difference. It always does.
> Also, if you want something done in 21.4, it can't hurt
to gently
> lobby Vin Shelton <acs(a)xemacs.org>, whose approval is required to
> apply the patch and release a new XEmacs in any case.
Vin, has anybody tested that patch in 21.4, and if so
are you willing to apply it?
For future cases: you should provide a reference to the relevant
messages even if it's already been mentioned (in that case just
copying the previous URL is fine).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
1:24 p.m.
New subject: indent-new-comment-line misbehaviour?
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Second, I see that this comes from something called
"newcomment.el",
so it may not work at all without the rest of the new comment stuff.
You may copy that whole file to ~/.xemacs and put
(load (expand-file-name "~/.xemacs/newcomment.elc"))
Now wait a moment so the solution is on the lisp level (newcomment)
not on the C level as a suspected. So there would be no need to
compile my own 21.5/21.4 just for that? I
Besides I see that the patch is from 2005-01-26 09:57:12 GMT
while in the xemacs-21.5.28 tree newcomment is from
2006-03-17, so I presume it is already patched.
in init.el after you've tested a bit by loading by hand (and the
very
first time you want to do M-x byte-compile-and-load-file on it).
Yes, we understand that. But this is part of the XEmacs core, so
(1) You need to wait for the Ubuntu process to pick up the next
release of XEmacs 21.4. We have zero control over that.
(2) They need to wait for us to release. Only Vin has much say in
that. He has been relatively actively posting recently, but he
doesn't post a schedule since XEmacs 21.4 is relatively bug-free
and releases are done as patches accumulate.
(3) The bug report and patch we have is obscure and old.
Your testing will make a big difference. It always does.
Right, but if its on the lisp level of course I am willing to do it
eagerly.
>
> Vin, has anybody tested that patch in 21.4, and if so
> are you willing to apply it?
For future cases: you should provide a reference to the relevant
messages even if it's already been mentioned (in that case just
copying the previous URL is fine).
Right, Reiner Steib has even a nifty function which does that. I have
to dig it out.
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
1:43 p.m.
New subject: indent-new-comment-line misbehaviour?
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
First things first. A patch to 21.5 may fail to apply to 21.4, but
you can probably get a copy of 21.5 version of that function from
http://hg.debian.org/hg/xemacs/xemacs, and put the defun in init.el,
where it will override the built-in.
Second, I see that this comes from something called
"newcomment.el",
so it may not work at all without the rest of the new comment stuff.
You may copy that whole file to ~/.xemacs and put
(load (expand-file-name "~/.xemacs/newcomment.elc"))
Okay some (bad) news for 21.4.
Byte compiling newcomment.el gave me
(void-function declare-fboundp)
Compiling file /home/oub/newcomment.el at Tue Jan 22 14:40:47 2008
While compiling the end of the data:
** the function declare-fboundp is not known to be defined.
So when I loaded the file and executed `indent-new-comment-line'
no surprise that I got an error which I attach.
Now the big question, I found out that declare-fboundp is defined in
bytecomp-runtime.el:
So either I could use the whole bytecomp-runtime or just catch declare-fboundp
any advice?
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2 p.m.
New subject: indent-new-comment-line misbehaviour?
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
First things first. A patch to 21.5 may fail to apply to 21.4, but
you can probably get a copy of 21.5 version of that function from
http://hg.debian.org/hg/xemacs/xemacs, and put the defun in init.el,
where it will override the built-in.
Second, I see that this comes from something called
"newcomment.el",
so it may not work at all without the rest of the new comment stuff.
You may copy that whole file to ~/.xemacs and put
(load (expand-file-name "~/.xemacs/newcomment.elc"))
Ok I used now bytecomp-runtime.el and the newcomment.el
indent-new-comment-line works now fine in *LaTeX* files but not in
lisp files
So the _new_ behavior is now:
I added a comment via `lisp-indent-for-comment'
(defun textmarker-region (start end) ;this is the comment
(interactive "r")
(xref-source-region start end)
(xref-target-region start end))
however then indent-new-comment-line put the cursor
(defun textmarker-region (start end) ;this is the comment
;;^
(interactive "r")
(xref-source-region start end)
(xref-target-region start end))
INSTEAD of
(defun textmarker-region (start end) ;this is the comment
;^
(interactive "r")
(xref-source-region start end)
(xref-target-region start end))
At least a ;; is added but the cursor is not in the right position.
Tested with 21.4.19 Mule.
Uwe
PS it seems that I post faster via gmane than via the mailing
list. Can somebody confirm this?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6149
days inactive
6150
days old
4 comments
2 participants
participants (2)
-
Stephen J. Turnbull -
Uwe Brauer