Keep to ASCII in subjects, please
16 years, 3 months
Stephen J. Turnbull
The recent issue entitled something like "XEmacs doen't display
control characters" was written using a pedantically correct
apostrophe. This was encoded in at least four different ways
(presumably by different mailers) because some got through, but at
least three related posts got spamtrapped in three different ways.
Each spamtrapped post shared a spitbucket with one or more real spam
posts. For that reason, I do not intend to relax these tests.
The Postmaster
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [Bug: 21.5-b28] CPerl mode: 'Wrong type argument: integer-or-marker-p, nil' on { keypress
16 years, 3 months
Aidan Kehoe
Ar an t-ochtú lá déag de mí Eanair, scríobh Ilya Zakharevich:
> On Fri, Jan 18, 2008 at 05:44:15PM +0100, Aidan Kehoe wrote:
> > > > Ilya, this is cperl-mode 5.23 with XEmacs 21.5.28, and the
> > > > debugger backtrace for the error is:
> > > >
> > > > Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
> > > > cperl-after-expr-p(nil "{;)")
> > > > cperl-electric-lbrace(nil)
> > > > call-interactively(cperl-electric-lbrace)
> > > >
> > > > See more details below.
> > >
> > > Sorry, this does not happen on my system. I think I need the result
> > > of debugging of non-byte-compiled version.
> >
> > Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
> > goto-char(nil)
> > (progn (goto-char (previous-single-property-change ... ...)) (beginning-of-line 0))
> > (if (get-text-property (point) (quote here-doc-group)) (progn (goto-char ...) (beginning-of-line 0)))
>
> I'm confused. The only place previous-single-property-change appears
> in the code the context is different...
Looks like Ville and I have the older version of cperl-mode.el that is in
the stable packages. The problem doesn’t appear with the version of
cperl-mode in the experimental packages directory.
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: XEmacs and GPLv3
16 years, 3 months
Gary Foster
I think you're confusing me stating "he has a point" with "he's
unequivocally correct".
I'm merely stating that he does have a point in stating that there is
serious overlap, he makes a valid point (albeit an incomplete one) and
it should be brought up in the discussion. I don't think Kastrup
(despite his consistent belligerence towards the XEmacs team in general
and his inability to converse civilly on a recurring basis) should be
dismissed out of hand. Whilst I don't believe he's completely correct,
I do believe the man has a valid discussion point this time. Even a
blind squirrel finds a nut every now and then. This isn't a binary
"he's 100% right or 100% wrong" sort of issue.
FWIW, I have some contributions (albeit not huge ones, the various
delete-key handling stuff and a few support packages like crisp.el) that
were licensed under the "GPL V2.0 or later" clause. While I (in
general) prefer V2 over V3 and I don't like being bullied into V3
licensing, I don't have a problem with my code being relicensed if the
whole project goes that way (which it looks like it is).
-- Gary F.
Stephen J. Turnbull wrote:
> Gary Foster writes:
>
> > Although it could've been phrased much more tactfully, the man does
> > have a point.
>
> Not really.
>
> I realize that copyleft as a matter of law inherently must impose
> severe restrictions on modes of sharing, so you might think that
> worrying about small differences like GPLv2+ vs GPLv3+ is a waste of
> worry. The point here is that copyleft provides nearly as little
> flexibility in mode to authors as proprietary licensing does. I don't
> blame them for asking for *what they want* even if that doesn't
> correspond very well to *what the law says the license means* (here
> "license" includes not only the GPL but the permissions language).
>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Fwd: Fwd: xemacs line & column numbers
16 years, 3 months
Vin Shelton
---------- Forwarded message ----------
From: Claude LEMOINE <claude.lemoine3(a)wanadoo.fr>
Date: Jan 18, 2008 5:45 PM
Subject: Re: Fwd: xemacs line & column numbers
To: Vin Shelton <acs(a)alumni.princeton.edu>
On Fri, 2008-01-18 at 17:34 -0500, Vin Shelton wrote:
> Claude -
>
> Thanks for your follow-up. Please don't drop xemacs-beta from the
> reply address. There are lots of people on the list with lots of
> contributions to make.
>
> So, it sounds to me like your modeline format has too much stuff in
> it, and the line/column info gets pushed off the screen. Is that
> correct?
>
> - Vin
>
You must be right: I have a lot of "----"going to the end of the line,
even farther, yet do not know how to change the format.
I do not know either where this additional stuff comes from;
not from my init files, maybe from the installation.
I might have installed too many optional packages on top of xemacs.
I will work on it this weekend, as it is now almost midnight in France
Thank You very much.
Claude.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Fwd: xemacs line & column numbers
16 years, 3 months
Vin Shelton
Claude -
Thanks for your follow-up. Please don't drop xemacs-beta from the
reply address. There are lots of people on the list with lots of
contributions to make.
So, it sounds to me like your modeline format has too much stuff in
it, and the line/column info gets pushed off the screen. Is that
correct?
- Vin
---------- Forwarded message ----------
From: Claude LEMOINE <claude.lemoine3(a)wanadoo.fr>
Date: Jan 18, 2008 4:40 PM
Subject: xemacs line & column numbers
To: acs(a)alumni.princeton.edu
Thank You for your so prompt answer !
I am running FC8 which is freshly installed (tuesday Jan 15)
with:
xemacs-21.5-b28 which is a beta version, yet the only one available with
yum and FC8:
installed by yum on wednesday with [yum install xemacs*]
Enclosed is the custom.el file that has been working fine for YEARS,
including FC6. (I never used FC7)
It is started with:
xemacs -fn -*-courier-medium-r-*-*-*-180-*-*-*-*-iso8859-* -geometry
132x46+150+0 ~/
The xemacs -vanilla shows correctly the lines and column numbers.
even after a [load-file custom.el] (the one attached) They do not show
at the same place as before in the bar, though.
When started with:
xemacs -geometry 132x46+150+0 ~/
the numbers do not show either. (the custom file is then automatically
loaded). same place as above in the bar.
The vanilla option seems to provide a better flavour :>]
Regards
`column-number-mode' is a variable declared in Lisp.
-- loaded from "/builddir/build/BUILD/xemacs-21.5.28/lisp/simple.elc"
Value: t
Documentation:
*Non-nil means display column number in mode line.
`line-number-mode' is a variable declared in Lisp.
-- loaded from "/builddir/build/BUILD/xemacs-21.5.28/lisp/simple.elc"
Value: t
Documentation:
*Non-nil means display line number in modeline.
The option/display/ pop up shows both setups activated.
Enclosed is the custom.el file that has been working fine for YEARS,
including FC6.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: XEmacs and GPLv3
16 years, 3 months
Julian Bradfield
In article <4790C15A.10400(a)gmail.com> Gary Foster <gary.foster(a)gmail.com> writes:
>Although it could've been phrased much more tactfully, the man does have
>a point.
What point? The only point I see is a need to learn some basic logic!
The OP wrote:
>>> Actually my preference would be to have it read "GPL V2 or later" to
David wrote:
>> It is nonsensical to pretend to permit releasing "GPL v2 or later" while
>> barring a release as "GPL v3 or later", since "GPL v3 or later" is
>> covered by "GPL v2 or later".
which is itself nonsense. If the OP wishes to retain the freedom of
his users to use the code under v2, a "GPL v3 or later" release must
be forbidden, since it does not permit the users to adopt v2.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: dvc?
16 years, 3 months
Skip Montanaro
Bug: XEmacs doesn’t display Control-characters correctly anymore
16 years, 3 months
Mike FABIAN
For details see
http://bugzilla.novell.com/show_bug.cgi?id=354705
XEmacs version is:
(emacs-version)
"XEmacs 21.5 (beta28) \"fuki\" (+CVS-20071205) [Lucid] (x86_64-suse-linux, Mule) of Mon Jan 14 2008 on magellan"
Problem description:
If one inserts a control character like Control-L or Control-M
in to an XEmacs buffer, these characters used to be displayed
as ^L and ^M respectively (One can input a Control-L by typing
C-q C-l).
Now, Control-L is just displayed as 'L', without the '^' in front
which makes it very hard to see. If there is a string which contained
such a Control character it used to look like for example
hello^Lworld
but now it looks like
helloLworld
When moving the cursor over this string, the cursor used to
sit on the ^ when reaching the Control-L, then jump to the
next character (here 'w') when moving it right.
Now, the cursor disappears completely when it reaches the Control-L
and appears again when the 'w' is reached.
This is very confusing and annoying.
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
I � Unicode
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
PDB Not Working in 21.5.28
16 years, 3 months
Kenneth Loafman
Here's the setup:
Ubuntu 7.10 (Gutsy)
AMD 64 X2
Built with:
./configure --prefix=/usr
make, etc.
All packages from SUMO originally, then updated against US Pre-Releases.
I get the following with Meta-X pdb
Structure formation error: Invalid prefix keys in sequence, ?/^A, ^X^A^L
Any ideas on how to proceed?
...Thanks,
...Ken
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
