Re: Welcome Andreas Roehler as python-modes package maintainer!
15 years, 10 months
Andreas Röhler
Stephen J. Turnbull wrote:
> I'm sorry for the delay on this. I've been buried in pain at work....
>
> Andreas,
>
> Welcome to the XEmacs Team as our python-modes maintainer!
[ ... ]
Thanks a lot, Steve, so here I am.
Let me express my special thanks to Skip, as the
maintainer in time, I detected python-mode.el as the
tool of choice. So I hope I'll be able to keep path as
Skip did.
Thanks to all making Emacsen such an enjoyable tools btw.
As already told, have some paper work to do next two
weeks. Basic steps should be taken nonetheless.
Andreas Röhler
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
BUG: vc does not work with branches, but in GNU emacs it does.
15 years, 10 months
Uwe Brauer
Hello
I think I better open a new thread.
I am using Xemacs 21.4.21 with vc pkg: 1.41.
together with the RCS backend.
According to
http://xtalk.msk.su/~ott/en/writings/emacs-vcs/EmacsVC.html#sec7
Vc should support branches using the command:
(vc-next-action 1)
(That is without the argument vc does not create branches.)
So what I expect is.
* creation and registration of file.
* add a new line check in. Check out
* want to create a branch 1.2.1 (will be numbered 1.2.1.1)
* continue with the branch modify it 1.2.1.2
* continue with the branch want to return to the tree
* modify and check in 1.4
GNU emacs does this, however Xemacs does not and I am wondering whether
the culprit is vc being too old.
Detailed explanation:
GNU emacs
1.1 first line insert Id and Log header, register
result:
--8<------------------------schnipp------------------------->8---
# $Id: test-rcs.txt,v 1.1 2009/01/29 11:34:17 oub Exp $
# $Log: test-rcs.txt,v $
# Revision 1.1 2009/01/29 11:34:17 oub
# Initial revision
#
First line, header register
--8<------------------------schnapp------------------------->8---
1.2 check out, add text and check in.
Result.
--8<------------------------schnipp------------------------->8---
# $Id: test-rcs.txt,v 1.2 2009/01/29 11:35:56 oub Exp $
# $Log: test-rcs.txt,v $
# Revision 1.2 2009/01/29 11:35:56 oub
# add text
#
# Revision 1.1 2009/01/29 11:34:17 oub
# Initial revision
#
First line, header register
1.2 add text
--8<------------------------schnapp------------------------->8---
1.2.1.1 create branch with (vc-next-action 1)
RESULT
--8<------------------------schnipp------------------------->8---
# $Id: test-rcs.txt,v 1.2.1.1 2009/01/29 11:37:00 oub Exp $
# $Log: test-rcs.txt,v $
# Revision 1.2.1.1 2009/01/29 11:37:00 oub
# this will be the branch 1.2.1
#
# Revision 1.2 2009/01/29 11:35:56 oub
# add text
#
# Revision 1.1 2009/01/29 11:34:17 oub
# Initial revision
#
First line, header register
1.2 add text
1.2.1.1 create branch
--8<------------------------schnapp------------------------->8---
NOTE modeline shows RCS-1.2.1.1
Check out, add text and check in (vc-next-action nil)
RESULT
--8<------------------------schnipp------------------------->8---
# $Id: test-rcs.txt,v 1.2.1.2 2009/01/29 11:39:20 oub Exp $
# $Log: test-rcs.txt,v $
# Revision 1.2.1.2 2009/01/29 11:39:20 oub
# branch 1.2.1.2
#
# Revision 1.2.1.1 2009/01/29 11:37:00 oub
# this will be the branch 1.2.1
#
# Revision 1.2 2009/01/29 11:35:56 oub
# add text
#
# Revision 1.1 2009/01/29 11:34:17 oub
# Initial revision
#
First line, header register
1.2 add text
1.2.1.1 create branch
1.2.1.2 add text and check in
--8<------------------------schnapp------------------------->8---
Return to the tree with (vc-next-action 1)
Modify and check in
RESULT.
--8<------------------------schnipp------------------------->8---
# $Id: test-rcs.txt,v 1.3 2009/01/29 11:40:46 oub Exp $
# $Log: test-rcs.txt,v $
# Revision 1.3 2009/01/29 11:40:46 oub
# 1.3 in tree
#
# Revision 1.2 2009/01/29 11:35:56 oub
# add text
#
# Revision 1.1 2009/01/29 11:34:17 oub
# Initial revision
#
First line, header register
1.2 add text
1.3 in tree
--8<------------------------schnapp------------------------->8---
XEMACS fails when it comes to (vc-next-action 1).
It creates the branch:
--8<------------------------schnipp------------------------->8---
%% $Id: test-rcs.txt,v 1.2.1.1 2009/01/29 11:25:38 oub Exp $
%% $Log: test-rcs.txt,v $
%% Revision 1.2.1.1 2009/01/29 11:25:38 oub
%% 1.2.1
%%
%% Revision 1.2 2009/01/29 11:25:13 oub
%% new lin
%%
%% Revision 1.1 2009/01/29 11:24:55 oub
%% Initial revision
%%
%% Time-stamp: <test-rcs.txt Changed by: Uwe Brauer, Thu Jan 29 12:25 2009>
First line and registration.
1.2 new line
1.2.1 start branch
--8<------------------------schnapp------------------------->8---
Note the Modeline only shows RCS-1.2 and not RCS-1.2.1.1 as GNUS
but when checking out the branch disappears and one is back in the tree
1.2
--8<------------------------schnipp------------------------->8---
%% $Id: test-rcs.txt,v 1.2 2009/01/29 11:25:13 oub Exp oub $
%% $Log: test-rcs.txt,v $
%% Revision 1.2 2009/01/29 11:25:13 oub
%% new lin
%%
%% Revision 1.1 2009/01/29 11:24:55 oub
%% Initial revision
%%
%% Time-stamp: <test-rcs.txt Changed by: Uwe Brauer, Thu Jan 29 12:25 2009>
First line and registration.
1.2 new line --8<------------------------schnapp------------------------->8---
Can anybody please confirm this??
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XEmacs 21.4.22 "Instant Classic" is released
15 years, 10 months
Vin Shelton
* XEmacs 21.4.22 "Instant Classic" is released.
"Instant Classic" is the Twentieth-Second in the OXYMORON series.
The latest stable release of XEmacs, XEmacs 21.4.22 - "Instant Classic",
is now available from xemacs.org and its mirrors.
* Availability
Anonymous ftp:
ftp://ftp.xemacs.org/pub/xemacs/xemacs-21.4
See http://www.xemacs.org/Install/. As of 21.4.18, only a source
tarball has been supplied. There was virtually no use of the info and
elc tarballs, so xemacs-21.4.22.tar.gz and xemacs-21.4.22.tar.bz2 are
the only tarballs supplied.
If you already have a 21.4.21 source tree, a patchkit is available in
xemacs-21.4.21-21.4.22.patch.gz. This does not update .elcs or .infos,
they will be rebuilt when you make XEmacs. If you have an earlier
version, you can repeatedly apply patchkits.
The tarballs and patches are signed with my GPG key, available from
most public keyservers and also from
ftp://ftp.xemacs.org/pub/xemacs/pgp-keys/vin_shelton.asc
Here are the MD5 check sums of each of the files related to the XEmacs
21.4.22 release:
47be4ace986a7c025017e75353fb33fe xemacs-21.4.21-21.4.22.patch.gz
c5effbfaf6f2d2d2b5a7ca8df845262d xemacs-21.4.21-21.4.22.patch.gz.asc
060bf7565cb3233c6e7071354e9a23a4 xemacs-21.4.22.tar.bz2
68c0c8dc349b47b5394b872fb1657790 xemacs-21.4.22.tar.bz2.asc
b0b762407316d6de170db69aba7a37cf xemacs-21.4.22.tar.gz
d0ee18c12f60a11f012c47b79209caf9 xemacs-21.4.22.tar.gz.asc
Also, if you don't have the packages yet, see
http://www.xemacs.org/Documentation/packageGuide.html.
Anonymous (pserver) CVS:
Anonymous CVS is available. We are very grateful to the staff at our
host, SunSITE.dk, for a lot of help and quick reponse to all our
requests.
If you haven't used XEmacs CVS recently, we moved the repository
before the 21.4.6 release. The repository structure is the same as
before, so it should be possible to reuse an existing checked-out CVS
tree.
Take care that your Root is set correctly to
CVSROOT=:pserver:cvs＠cvs.xemacs.org:/pack/xemacscvs
On platforms with a Bourne shell and find available, something like
for r in `find . -name Root`; do echo $CVSROOT > $r; done
will convert your entire tree.
Tags are also the same; to update to release 21.4.22, use the release
tag "r21-4-22". To set a sticky tag which will always update to the
current release, use the branch tag "release-21-4".
For more details, see
http://www.xemacs.org/Develop/cvsaccess.html
* Brief summary of changes to XEmacs 21.4.22 "Instant Classic"
User-Visible Bug Fixes and Improvements
Fix: Compile fixes for GTK+
Fix: Fix printing on non-mswindows systems. (See
http://tracker.xemacs.org/XEmacs/its/issue124).
Fix: Fix at_dot regex matching.
Fix: Fix off-by-one error in mule-ccl.
Fix: Move operator definitions to autoload-operators.el and use them.
This patch restores the building of packages in XEmacs 21.4.
Fix: Increase connection retries in winclient.c.
Fix: Fix compilation under Cygwin 1.7.
Update: Update Vin Shelton's bio.
Feature: Support Intel C compiler under Windows.
-------- ChangeLog Entries from ChangeLog --------
2008-12-28 Vin Shelton <acs(a)xemacs.org>
* XEmacs 21.4.22 is released
2007-11-22 Vin Shelton <acs(a)xemacs.org>
* etc/photos/vin.png:
* etc/photos/vinm.png: Updated.
-------- ChangeLog Entries from lib-src/ChangeLog --------
2008-12-28 Vin Shelton <acs(a)xemacs.org>
* XEmacs 21.4.22 is released
2008-01-09 Vin Shelton <acs(a)xemacs.org>
* winclient.c: Create CONNECT_RETRIES and increase retry count
from 5 to 10.
-------- ChangeLog Entries from lisp/ChangeLog --------
2008-12-28 Vin Shelton <acs(a)xemacs.org>
* XEmacs 21.4.22 is released
2008-12-30 Vin Shelton <acs(a)xemacs.org>
* easy-mmode.el: Added easy-mmode.el so autoload.el will work
during building even if no packages are found.
2008-05-13 Aidan Kehoe <kehoea(a)parhasard.net>
* printer.el (generic-print-region):
(generic-print-buffer):
Use #'valid-device-type-p instead of #'valid-specifier-tag-p to
check if the msprinter device is available, now that msprinter is
always available as a specifier tag.
2008-12-24 Vin Shelton <acs(a)xemacs.org>
* about.el: Add Francisco to my bio!
2008-12-23 Vin Shelton <acs(a)xemacs.org>
* autoload.el: Move operator definitions to autoload-operators.el
in the xemacs-base package.
2007-11-22 Vin Shelton <acs(a)xemacs.org>
* about.el (about-hacker-contribution): Updated my bio.
-------- ChangeLog Entries from lwlib/ChangeLog --------
2008-12-28 Vin Shelton <acs(a)xemacs.org>
* XEmacs 21.4.22 is released
-------- ChangeLog Entries from man/ChangeLog --------
2008-12-28 Vin Shelton <acs(a)xemacs.org>
* XEmacs 21.4.22 is released
-------- ChangeLog Entries from netinstall/ChangeLog --------
2008-12-28 Vin Shelton <acs(a)xemacs.org>
* XEmacs 21.4.22 is released
-------- ChangeLog Entries from nt/ChangeLog --------
2008-12-28 Vin Shelton <acs(a)xemacs.org>
* XEmacs 21.4.22 is released
2008-01-18 Vin Shelton <acs(a)xemacs.org>
* xemacs.mak: Support Intel C compiler.
-------- ChangeLog Entries from src/ChangeLog --------
2008-12-28 Vin Shelton <acs(a)xemacs.org>
* XEmacs 21.4.22 is released
2008-12-27 Vin Shelton <acs(a)xemacs.org>
* syswindows.h: Don't define wide character interfaces for Cygwin
1.7 and up.
2008-03-05 Dominique Quatravaux <domq(a)cpan.org>
* glyphs-gtk.c: Fixed compilation under gcc 4.x.
2008-11-01 Stephen J. Turnbull <stephen(a)xemacs.org>
* regex.c (re_search_2): Fix at_dot by changing charpos to bytepos.
From Julian Bradfield <18654.1143.304851.782755(a)krk.inf.ed.ac.uk>.
2008-12-25 Vin Shelton <acs(a)xemacs.org>
* mule-ccl.c (ccl_driver): Fix off-by-one error.
By Julian Bradfield in
<18691.16568.526264.972026(a)krk.inf.ed.ac.uk>.
* mule-ccl.c (ccl_driver):
-------- ChangeLog Entries from tests/ChangeLog --------
2008-12-28 Vin Shelton <acs(a)xemacs.org>
* XEmacs 21.4.22 is released
2008-09-27 Stephen J. Turnbull <stephen(a)xemacs.org>
* automated/regexp-tests.el: Add test for at_dot regexp.
Sincerely,
Vin Shelton
Stable Release Manager for XEmacs
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
char-classes, thingatpt-utils
15 years, 10 months
Andreas Röhler
Hi all,
I've made most char-classes known as [[:alnum:]]
etc. from GNU Emacs available for my
`thingatpt-utils' with XEmacs too.
Maybe call `alnum-atpt' etc. to watch it. Wrote
char-classes here with a x-, not to mix up.
For the moment its done that way:
(when (featurep 'xemacs) (setq x-alnum "[a-zA-ZäöüßÄÖÜ0-9]"))
(when (featurep 'xemacs) (setq x-alpha "[a-zA-ZäöüßÄÖÜ]"))
(when (featurep 'xemacs) (setq x-ascii "[\000-\177]"))
(when (featurep 'xemacs) (setq x-blank "[ \t]"))
(when (featurep 'xemacs) (setq x-cntrl "[\000-\006]\016-\037]"))
(when (featurep 'xemacs) (setq x-digit "[0-9]"))
(when (featurep 'xemacs) (setq x-graph "[\041-\177\241-\377]"))
(when (featurep 'xemacs) (setq x-lower "[a-zäöüß]"))
(when (featurep 'xemacs) (setq x-multibyte ""))
(when (featurep 'xemacs) (setq x-nonascii "[^\040-\177]"))
(when (featurep 'xemacs) (setq x-print "[\041-\177\241-\377]"))
(when (featurep 'xemacs) (setq x-punct "[.,-_:;?!]"))
(when (featurep 'xemacs) (setq x-space "[ \t]"))
(when (featurep 'xemacs) (setq x-unibyte ""))
(when (featurep 'xemacs) (setq x-upper "[A-ZÄÖÜ]"))
(when (featurep 'xemacs) (setq x-xdigit "[0-9.,]"))
As you see, some problems remain. Any suggestions for
x-unibyte, x-multibyte and in general?
Thanks
Andreas Röhler
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [Bug: 21.4.22] Window height 0 too small (after splitting)
15 years, 10 months
Rodney Sparapani
Rodney Sparapani wrote:
>
> Interesting. Maybe a little more detail would help you. So, when
> I do a Save As..., the dialog windows pops up, but instead of allowing me to
> enter or select a file name, the dialog window has the file contents
> in the upper half and the lower half has the *backtrace*. It seems
> to be confused as to which window (or frame?) it is in. But, I guess
> this may all be a side-effect rather than the cause.
>
Perhaps you expected this... But, it is not just the Save As... dialog.
Open in New Frame triggers it as well. And again, only with .tex files.
It doesn't matter what's in the file.
Rodney
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: 1.45 generates branches but can't go back to the tree
15 years, 11 months
Uwe Brauer
>>>>> "Stephen" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
> Uwe Brauer writes:
>> *however* can you successfully move out the branch and return to the
>> tree??
>>
>> I can't if I try to return (using C-u C-x v v)
> Yes, I can change versions to an existing version. I needed to
> revert to "master" first. I think C-x v v is very sensitive to
> exactly where you are in the cycle.
So if you don't revert to master, does it work?
Since I can't use the menu, see my other posting it is not entirely
clear to me how to return to master.
I played around with various checks in and out I am offered to return to
master, and then indeed C-u C-x v v works, still sort of odd.
Hm in GNU emacs I don't have to revert to master.
> I don't see the errors you do (I haven't tried very much yet, but
> things seem to work pretty smoothly).
> I'm not sure what's going on with the crash. If you can reproduce
> it, try running under the debugger and see if you can get a
> backtrace.
You mean the C bugger because lisp bugger will not work since it crashes
immediately.
I think I have to activate the C-bugger which is deactivated in Kubuntu
for and I don't remember how to activate it.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
cv (rcs) how to generate branches
15 years, 11 months
Uwe Brauer
Hello
I am using for quite a long time the vc package, and the RCS[1] backend.
What I am missing most is the possibility to generate branches of a
version.
Scrolling throw the man pages of RCS is seems that RCS supports branches
but I can't find anything in vc which would support that.
Anybody knows about it?
Uwe Brauer
[1] I could use CVS but honestly that looks to complicated to me, for
the moment.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
bug updating a bug in your issue tracker
15 years, 11 months
Greg Klanderman
Hi,
I'm trying to update issue #350 to note that it is very likely a
duplicate of issue #331 (which I submitted). However, clicking the
submit changes button gives the error:
| DetectorError: Error: couldn't send email: {'glynn': (501, ':
| recipient address must contain a domain')}
followed by a long HTML-ified python backtrace.
Could someone do something about this for me? It seems Vladimir
recently updated this bug successfully, though I'm not sure how.
Why on earth did you choose such a horrid bug tracking system?
cheers,
Greg
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [Python-mode] FSF assignment policy
15 years, 11 months
Andreas Röhler
Eric S. Johansson wrote:
> Andreas Roehler wrote:
>> Hi (X)Emacs folks,
>>
>> as FSF assignment policy was raised again at
>> python-mode(a)python.org, please permit to ask you a
>> thing I never understood:
>>
>> AFAIS every Emacs-file is inspired by many, many others
>> from the very beginning. We see almost always a plenty
>> of revisions with a lot of people involved.
>>
>> So how a single developer could ever declare what the
>> assignment formula demands? How could any person
>> declare, he _owns_ the rights at the code, thus
>> assigning it.
>>
>> Isn't that assignment policy driving developers in a
>> kind of forgery? Making them false declarations,
>> thus having rights about them, being everyday able to
>> sue them for these false declarations?
>>
>> Or am I simply dreaming a bad dream?
>
> actually, I would call it an affectation. Before my hands failed, I could
> afford the luxury of a strict GPL stance. After all, I had no trouble taking a
> few extra steps for political purity. Now, I live by the rule that
> functionality trumps politics. I do what I must so I can earn a living using
> whatever tools I have available. EULA's or GPL, I ignore licensing restrictions
> if they get in the way.
>
> I now see political stances on licensing as an affectation to gain attention.
> These attitudes have led us to ignoring many good pieces of software ignoring
> (JFS.ZFS) and people putting effort into redundant work (est4,btrfs). It has
> kept Linux having good handicapped accessibility, especially in my area of
> interest, accessible via speech recognition. We have a good solution with
> NaturallySpeaking and wine but, it's not ideologically pure.
>
> As you can see, I only see these licensing arguments as an impediment to people
> getting things done with a minimum amount of effort. You've created some
> changes that I am trying to incorporate into a speech grammar and for that I'm
> thankful.
Great to hear. Don't hesitate to tell which things you need still, what Emacs
should do in which circumstances.
Some reporting mode, saying after a close-block etc. where you are, what has been closed,
is worked on already.
BTW: Do have a site with your implementation which I could visit?
Should you know some stuff to read about the issue, please tell.
Do me a favor, hold your nose, and just sign the damn papers
Well, that not so easy. Things are much more serious IMO. In any case programs
published here will be GPL as far as it concerns me, so it shouldn't matter for
the user if its assigned to FSF or not.
and
> let's get on with the task at hand.
>
>
> ---eric
>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta