ACTIVITY SUMMARY (2011-07-19 - 2011-07-26)
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.
536 open ( +2) / 250 closed ( +1) / 786 total ( +3)
Open issues with patches: 12
Average duration of open issues: 897 days.
Median duration of open issues: 969 days.
Open Issues Breakdown
new 197 ( +2)
deferred 6 ( +0)
napping 4 ( +0)
verified 54 ( +0)
assigned 153 ( +0)
committed 29 ( +0)
documented 3 ( +0)
done/needs work 24 ( +0)
Issues Created Or Reopened (3)
______________________________
Menubar accelerator code autoselects "[" in VM menubar. 2011-07-21
http://tracker.xemacs.org/XEmacs/its/issue786 created stephen
gnus cannot send emails using smtp with starttls (i.e. gmail) 2011-07-25
CLOSED http://tracker.xemacs.org/XEmacs/its/issue787 created anonymous
gnus cannot send emails using smtp with starttls (i.e. gmail) 2011-07-25
http://tracker.xemacs.org/XEmacs/its/issue788 created jarl
Issues Now Closed (1)
_____________________
gnus cannot send emails using smtp with starttls (i.e. gmail) 0 days
http://tracker.xemacs.org/XEmacs/its/issue787 jarl
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Štěpán Němec writes:
> > features like buffers, then according to the Honorary Dr. Stallman and
> > his Leagle Beagle, that's linking, and the GPL requires that that code
> > be distributed under the terms of the GPL or not at all, until there
> > is an implementation of Emacs Lisp that isn't derived from GNU Emacs.
>
> Please tell me you're kidding. Do you have any source for that?
Sorry, that would be a lie. :-/ The source is a private communication
from His High Gnuisance himself. There's also this:
http://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL
Evidently, if you `require' any GPL-ed libraries, you're done for.
Even if you don't, Richard told me that use of Emacs-specific
"facilities" like buffers is what is meant by "'bindings' to other
facilities (often, but not necessarily, libraries)" in that FAQ.
> In any case, I do know about non-GPL Elisp code, and I don't use
> GPL for anything I write either.
Well, they and you are at some risk, then. I doubt it's very much, as
the FAQ is rather ambiguous, the Emacs Lisp manual *does* describe
buffers etc as part of the language, and as long as you only
distribute your code and not Emacs itself the FSF is at much greater
risk, as many competent lawyers believe that copyright law does *not*
imply that dynamic linking is derivation unless you distribute the
original work "with" your own code. If you decided to challenge their
claim, they'd be in very big trouble if you won -- the whole GPL
vs. LGPL distinction vanishes into thin air (although it would be very
expensive for anyone to fight them in court, and they have a long
history of using that to intimidate people). So the FSF is unlikely
to go after individuals or non-Emacs projects IMO.
XEmacs, however, is a much fatter target for them as they can go after
us on the grounds that XEmacs + the packages constitute a single
product, and the whole thing is a derivative work of GNU Emacs. If
they lose that, they just say, oh, we're sorry, and nobody will ever
mention the dynamic linking aspect.
> IMO it's (been for a long time) definitely time to have a decent libre
> Emacs implementation (I'd love to have a Schemacs[1], anyone?)
That's a very big project if you don't think the other programs you
mentioned are good enough. Mike (Sperber)'s student did some work on
implementing Emacs Lisp in Scheme48, which would get us partway
there.[1] But then we'd have a huge amount of effort, which nobody
involved in (SX|X)?Emacs development could safely be involved in, to
create the compatible API to things like buffers and strings. I don't
think such a thing is likely to happen soon, so the most plausible
route would be a Schemacs core engine, based on a libre-licensed
Scheme, combined with UI and API derived from (SX|X)?Emacs, with the
whole work licensed under GPL.
It would be somewhat easier to drop Emacs (and XEmacs) compatibility,
but as I say, if the programs you mention aren't good enough, then
we're a very long way from accomplishing that.
Footnotes:
[1] The specific result was that an Elisp interpreter with
appropriate semantics for variables etc written in Scheme48 got within
spitting distance of native Elisp performance. But this was only for
Lisp-y constructs, not for things like buffers and UI.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi,
I've been trying to get the mode for go-lang working with XEmacs 21.5
and I think it is solved (Some patches to the mode and with the recent
syntax-ppss-patch applied in XEmacs.)
My goal was to include the go-lang mode in prog-modes in the
packages. But will that be OK? I assume here that the other modes in
prog-modes eventually will be GPLv3 or later due to syncing. Can they
live side by side with a BSD-like licensed file?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2011-07-12 - 2011-07-19)
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.
534 open ( +2) / 249 closed ( +0) / 783 total ( +2)
Open issues with patches: 12
Average duration of open issues: 894 days.
Median duration of open issues: 962 days.
Open Issues Breakdown
new 195 ( +2)
deferred 6 ( +0)
napping 4 ( +0)
verified 54 ( +0)
assigned 153 ( +0)
committed 29 ( +0)
documented 3 ( +0)
done/needs work 24 ( +0)
Issues Created Or Reopened (2)
______________________________
switching x screens, pointer glyph not caching/should be, or v 2011-07-12
http://tracker.xemacs.org/XEmacs/its/issue784 created anonymous
tty frame resets modeline colors 2011-07-13
http://tracker.xemacs.org/XEmacs/its/issue785 created hasm
Top Issues Most Discussed (1)
_____________________________
3 (make-glyph ... :data ...) on tty 20 days
assigned http://tracker.xemacs.org/XEmacs/its/issue778
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
A couple of users have reported warnings on 21.5.31 when using
"gnuclient -nw" and XEmacs has a graphics image that was created using
(make-glyph ... :data ...). See issue778 for details (including the
values of the :data-based and :file-based glyphs that I talk about
below).
I'd like some guidance on how the code is supposed to work.
First question: as described in issue778, the test-case glyph from MH-E
is different depending on whether it was created using :data or :file.
With:data, the specifier has tty and stream clauses that it lacks when
created with :file. Is that to be expected?
Second question: suppose a buffer is created containing one of these
:data glyphs while the current frame is an X window, and then the buffer
is then viewed in a tty frame. With 21.5.31, the user gets warnings.
With 21.5.29+0d436a78c514, there are no warnings, even though the
glyph's specifier still has those tty and stream clauses. Is this
new warning expected?
thanks,
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
I was trying to get xpm-mode to display different cursors at different
times, and had a little trouble getting the pointer to change. I thought I
would mention it here, as I'm not sure that the behavior is intentional.
Based on the Lispref->Glyphs->Using Glyphs->External-Glyphs section of the
documentation, I thought I should be able to pass an image instantiator into
set-glyph-image; something like:
(set-glyph-image text-pointer-glyph [ xpm :file
"I://xemacs_macros//test.xpm" ])
And indeed, that changes the pointer over the text just fine on a fresh
launch of xemacs. However, repeated calls to the same command (with
different images) have no effect.
I also tried making an image specifier from the icon, and using that instead
but it behaved the same; I could change the pointer once, but not again.
I'm assuming that this means that the specifier doesn't have a value for the
global locale to start with, and so the first command works. After that
however, for some reason it can't override
that with newer specifications. I also tried setting HOW-TO-ADD to
'remove-all, but that didn't affect things at all.
What I found that did work was to pass in an image instance to
set-glyph-image:
(set-glyph-image text-pointer-glyph (make-image-instance [ xpm :file
"I://xemacs_macros//test.xpm" ] nil 'pointer))
Using image instances, I could repeatedly change the pointer. However, I
noticed in the set-glyph-image doc string that an image instance isn't even
listed as a valid input.
I'm not sure why exactly an instance behaves differently from an
instantiator, or if there is some extra command I would need to run to
update to the new cursor when using an instantiator.
If you could shed some light on this, I would be grateful. I'm also
attaching a pair of small cursor xpms I was using for testing.
Sincerely,
Byrel
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Jerry James <james(a)xemacs.org> writes:
> On Wed, Jul 13, 2011 at 5:16 AM, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
>> Good. I wish I could recommend Tux, but none of the good ol' boys are
>> left in the administration, we'd have to do all the real work
>> ourselves and fight the Tux demigods on top of that. :-)
>>
>> I just had another legit expense questioned by Accounting. Maybe I
>> can find a backdoor so the Ministry of Education will pay for a real
>> XEmacs server ... nah, too risky, but fun to fantasize about ....
>
> Does anybody know how much it would cost to get some good hosting?
> I'm willing to kick in 100 trillion dollars [1].
Around here, around $20-$30 per month. But I'm sure we could get into
bitbucket, for example.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2011-07-05 - 2011-07-12)
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.
532 open ( +1) / 249 closed ( +0) / 781 total ( +1)
Open issues with patches: 12
Average duration of open issues: 890 days.
Median duration of open issues: 955 days.
Open Issues Breakdown
new 193 ( +1)
deferred 6 ( +0)
napping 4 ( +0)
verified 54 ( +0)
assigned 153 ( +0)
committed 29 ( +0)
documented 3 ( +0)
done/needs work 24 ( +0)
Issues Created Or Reopened (2)
______________________________
No-mule XEmacs can corrupt UTF-8 files. 2011-07-12
http://tracker.xemacs.org/XEmacs/its/issue780 reopened stephen
Bug reports should list non-default customizations. 2011-07-12
http://tracker.xemacs.org/XEmacs/its/issue783 created stephen
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta