8:23 a.m.
Both emacs and vim handle recoloring multi-line objects like strings, etc. Xemacs
doesn't.
For example, in this python code fragment:
class foo:
""" This is line 1 of a multi-line comment
this is line 2 of that comment
and finally, this is line 3"""
...
It colorizes correctly initially, but loses track of everything not on the line being
edited when changing the comment chars.
Is there any work going on to fix that? How might someone (like me0 ignorant of the
xemacs internals help?
I found someone commenting on this a year or two ago, indicating a path to a solution, but
i can't find anything about it now.
Thanks!
-- Perry
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
9:20 p.m.
Perry Wagle <wagle(a)mac.com> writes:
Both emacs and vim handle recoloring multi-line objects like
strings,
etc. Xemacs doesn't.
[...]
It colorizes correctly initially, but loses track of everything not on
the line being edited when changing the comment chars.
Emacs' version of font-lock has evolved a lot but cannot be synched
easily, mostly for licensing reasons as far as I know.
Is there any work going on to fix that?
People here at XEmacs are spending quite a bit of their time into
relicensing XEmacs to GPLv3, so that code merges from Emacs will be
possible again. I am sure Emacs font-lock (or parts of it) has a high
priority since -- as you noticed -- it directly affects how people
perceive the quality of XEmacs.
Stephen T. might object (and he knows better than I), but I don't
think that changing/fixing current XEmacs font-lock is worth
considering. Coincidentally I have had a close look at it in the past
couple of days. There are some issues some of which might even be easy
to fix, but don't think it makes much sense at this point.
--
Marcus
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:58 a.m.
Marcus Harnisch writes:
Emacs' version of font-lock has evolved a lot but cannot be
synched
easily, mostly for licensing reasons as far as I know.
It's worse than that, but the biggee is licensing.
Stephen T. might object (and he knows better than I), but I
don't
think that changing/fixing current XEmacs font-lock is worth
considering.
I don't know enough about font-lock to object; I'm not a big fan of it
in any case. I know that nxhtml, which I'd really like to have, hooks
into Emacs's font-lock at a low level and can't easily be ported to
XEmacs Lisp. So I'm +0.5 on "don't fix, synch" at the moment.
Coincidentally I have had a close look at it in the past couple of
days. There are some issues some of which might even be easy to
fix, but don't think it makes much sense at this point.
If you want to get started on synching, feel free. :-)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:40 p.m.
On Jan 2, 2011, at 8:58 PM, Stephen J. Turnbull wrote:
Marcus Harnisch writes:
> Emacs' version of font-lock has evolved a lot but cannot be synched
> easily, mostly for licensing reasons as far as I know.
It's worse than that, but the biggee is licensing.
What's the expected/guessed-at timeframe for solving the licensing issues?
I'm tempted to try to help, since I really need this to work, but my burners are
already overflowing with too-many-projects.
-- Perry
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
6:04 p.m.
Perry Wagle writes:
What's the expected/guessed-at timeframe for solving the
licensing issues?
I expect the cleanup to be actually done within days (but wait for a
post from Mats Lidell who's actually doing most of the work at this
point in time). When that's done, there will be a "big bang" merge
from his workspace, and work on synching the 21.5 core code to GNU
Emacs can start.
I'm preparing for overseas travel next week, and then life will be
absolutely insane for about 2 weeks, so I would guess I'll be able to
do a GPLv3 release in the first week of February. At that point, any
code in project (except for XEmacs 21.4 but including packages) will
be fair game for synching to GPLv3 code. In the meantime, publishing
mixtures of XEmacs and GNU code in the packages will be somewhat of a
grey area. After that, the packages can pretty much be relicensed as
GPLv3 or later as need arises (ie, when somebody syncs GPLv3 code in a
package, they'll need to fix up the permission notices as well).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
10:08 p.m.
>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
Stephen> I expect the cleanup to be actually done within days (but wait for a
Stephen> post from Mats Lidell who's actually doing most of the work at this
Stephen> point in time).
I have something like 10 files left on the todo-list. Look for the
"GPLv3|L8R"-tag in the mail archive for some postings about files left
etc to get a feeling for what has been going on and the issues we have
had, and are having.
Stephen> When that's done, there will be a "big bang" merge from his
Stephen> workspace, and work on synching the 21.5 core code to GNU
Stephen> Emacs can start.
The problem I see is the definition of done. When I'm done with the
10-files-to-go I think we really need an inspection before we do the
big bang. I know that I have not updating the ChangeLogs in all
cases. That might need to be fixed. There might also be files that I
have made bad assumptions about although we have discussed them on the
list. So it would be good to have a few more eyes on it before
committing.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:11 p.m.
On 01/ 5/11 04:08 PM, Mats Lidell wrote:
The problem I see is the definition of done. When I'm done with
the
10-files-to-go I think we really need an inspection before we do the
big bang. I know that I have not updating the ChangeLogs in all
cases. That might need to be fixed. There might also be files that I
have made bad assumptions about although we have discussed them on the
list. So it would be good to have a few more eyes on it before
committing.
Yours
But, that doesn't mean people should not start synching their favorite
Emacs lisp file does it? Having done this poorly in the past, I can
say that it can be very time-consuming. Most likely you will finish
what you are doing before a complicated package like comint or gnus
is working. And, even so, then it goes in the pre-release, or whatever
it is called, and stays there for ages ;o)
Rodney
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
11:29 p.m.
>>>> Rodney Sparapani <rsparapa(a)mcw.edu> writes:
Rodney> But, that doesn't mean people should not start synching their
Rodney> favorite Emacs lisp file does it?
I guess it is mostly a matter of belief. If you don't need to have the
GPLv3 version available in real life, before you feel motivated to
start a sync of a package, then why not do it.
The first GPLv3 version will just be a license change. So no new
functionality. This might cause practical problems for a sync because
the new code you are syncing with might depend on new features that we
don't have, yet.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:06 a.m.
Rodney Sparapani writes:
But, that doesn't mean people should not start synching their
favorite
Emacs lisp file does it?
Very good point!
You can *always* do anything you like with GPLed software as long as
it stays on your workstation, or if it is used in your job, you can
share it with your employer (and if your employer is a *corporation*,
you can share with other employees).
I hope that people *are* already synching privately, that's what the
GPL is designed to encourage. When I say synching is "problematic", I
mean synching a *public repository*.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
10:53 p.m.
New subject: GPLv3|L8R done!? (was: multi-line colorization)
>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
Stephen> I expect the cleanup to be actually done within days (but
Stephen> wait for a post from Mats Lidell who's actually doing most of
Stephen> the work at this point in time).
Well, I think it is done now. I fail to find any more files to
convert, fix, replace or delete anyway.
So what we have at the moment is a repository with the GPLv3 version
that is open to developers only. We need to turn, merge, that into the
trunk open for everyone.
Stephen> When that's done, there will be a "big bang" merge from his
Stephen> workspace, and work on synching the 21.5 core code to GNU
Stephen> Emacs can start.
Would a release of the current 21.5 be appropriate before the merge or
does a simple tag suffice?
And, I feel I have been nagging about this for a while, the
GPLv3-branch really needs some inspection. If you are a developer
please feel free to check out and inspect the branch.
Stephen> I'm preparing for overseas travel next week, and then life
Stephen> will be absolutely insane for about 2 weeks, so I would guess
Stephen> I'll be able to do a GPLv3 release in the first week of
Stephen> February.
First week of February is approaching rapidly. The exact date of the
release isn't so important but we need to setup a plan. Like whether
there will be a 21.5 release from the current trunk before the merge,
if the GPLv3-branch should be inspected before or after the merge etc,
etc. So we can coordinate our efforts. Please let me know if there is
anything I can do to help you with the release.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:57 p.m.
On Thu, 06 Jan 2011 03:04:33 +0900, Stephen wrote:
so I would guess I'll be able to do a GPLv3 release in the first
week of February.
The first week of March has now come and gone - what is the current
status on this?
Is there anything any of us can do to help? What are the roadblocks?
Best regards,
Adam
--
"I always liked songs with parentheses in the title." Adam Sjøgren
asjo(a)koldfront.dk
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:22 a.m.
Adam Sjøgren writes:
Is there anything any of us can do to help? What are the
roadblocks?
The main roadblock right now is day (and often night) job. I thought
things should lighten up around mid-February, but that turned out not
to be the case. Get me fired, and I'll have some time to work on it.
Maybe. ;-)
It's also hard to build up much enthusiasm for losing sleep in order
to condense about 100kB of ChangeLogs into release notes when AFAIK
there are no patches in the queue that require a GPLv3 XEmacs before
they can be applied.
XEmacs cannot incorporate such patches until the license conversion
takes place. However, that doesn't stop you from developing and
submitting them -- you can do anything you want in that respect on
your own machine, and submit the result with a GPLv3+ license clearly
stated. Once they start coming in, it will be much harder to choose
sleep over XEmacs. :-)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:42 p.m.
New subject: GPLv3 packages (was multi-line colorization)
Stephen J. Turnbull wrote:
It's also hard to build up much enthusiasm for losing sleep in
order
to condense about 100kB of ChangeLogs into release notes when AFAIK
there are no patches in the queue that require a GPLv3 XEmacs before
they can be applied.
Where are we with respect to GPLv3+ packages? I have a newer version of
Gnus in my queue, which I haven't done anything with because it's
GPLv3+. Can I move forward with it, or do I have to wait for the
license change for the core code?
thanks,
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:15 p.m.
New subject: GPLv3 packages (was multi-line colorization)
Mike Kupfer writes:
Stephen J. Turnbull wrote:
> It's also hard to build up much enthusiasm for losing sleep in order
> to condense about 100kB of ChangeLogs into release notes when AFAIK
> there are no patches in the queue that require a GPLv3 XEmacs before
> they can be applied.
Where are we with respect to GPLv3+ packages? I have a newer version of
Gnus in my queue, which I haven't done anything with because it's
GPLv3+. Can I move forward with it, or do I have to wait for the
license change for the core code?
To the extent that these are *XEmacs* packages, probably you should
wait. OTOH, there already *is* a GPLv3 program that uses the packages
by design (SXEmacs). So it may be OK if you say it's for use with
SXEmacs. Ask the FSF copyright clerk or a lawyer. :-(
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:38 p.m.
New subject: GPLv3 packages (was multi-line colorization)
On Tue, Mar 8, 2011 at 11:15 AM, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
Mike Kupfer writes:
> Stephen J. Turnbull wrote:
>
> > It's also hard to build up much enthusiasm for losing sleep in order
> > to condense about 100kB of ChangeLogs into release notes when AFAIK
> > there are no patches in the queue that require a GPLv3 XEmacs before
> > they can be applied.
>
> Where are we with respect to GPLv3+ packages? I have a newer version of
> Gnus in my queue, which I haven't done anything with because it's
> GPLv3+. Can I move forward with it, or do I have to wait for the
> license change for the core code?
To the extent that these are *XEmacs* packages, probably you should
wait. OTOH, there already *is* a GPLv3 program that uses the packages
by design (SXEmacs). So it may be OK if you say it's for use with
SXEmacs. Ask the FSF copyright clerk or a lawyer. :-(
Stephen -
Isn't this exactly the round tuit you requested????
Please make a GPL3 release.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
6:02 a.m.
New subject: GPLv3 packages (was multi-line colorization)
Vin Shelton writes:
Isn't this exactly the round tuit you requested????
*My* round tuit has to do with day job. But yes, that's some
incentive to work on the release.
Please make a GPL3 release.
I started working on it last night, but I'm making more mistakes than
progress. I need more sleep.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:47 p.m.
New subject: GPLv3 packages (was multi-line colorization)
Stephen J. Turnbull wrote:
I started working on it last night, but I'm making more mistakes
than
progress. I need more sleep.
I wholeheartedly endorse getting enough sleep. :-)
Please don't feel pressured on my account. Yes, I have a new version of
Gnus I'd like to commit, but I have other things I need to do first,
like taxes.
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5007
days inactive
5076
days old
16 comments
8 participants
participants (8)
-
Adam Sjøgren -
Marcus Harnisch -
Mike Kupfer -
Perry Wagle -
Rodney Sparapani -
Stephen J. Turnbull -
The XEmacs Package Smoketest -
Vin Shelton