Jerome Quelin <[EMAIL PROTECTED]> writes:
> And the minibuffer tells me:
> Symbol's function definition is void: line-beginning-position
>
> I'm using xemacs 21.4.14
You could put something like:
(defalias 'line-beginning-position 'point-at-bol)
in your XEmacs init file.
How about defining a co
--- Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Joshua Gatcomb <[EMAIL PROTECTED]> wrote:
>
> > After the change - case 3 now prints thread 1.
>
> Strange.
indeed
> > You mentioned in the previous email that you were
> > interested in knowing if this was Windows IO or
> the
> > Cygwin varian
On Fri, Oct 01, 2004 at 06:09:37PM +0200, Jerome Quelin wrote:
> Hi,
>
> I tried the pir-mode provided in the editor/ subdir. And when opening a
> .imc file (I've associated .pir with pir-mode + font-lock-mode), I
> cannot type spaces or carriage returns:
>
> (24) (warning/warning) Error caught i
Hi,
I tried the pir-mode provided in the editor/ subdir. And when opening a
.imc file (I've associated .pir with pir-mode + font-lock-mode), I
cannot type spaces or carriage returns:
(24) (warning/warning) Error caught in `font-lock-pre-idle-hook':
(invalid-regexp Invalid syntax designator)
And
Leopold Toetsch wrote:
Kj <[EMAIL PROTECTED]> wrote:
But what is actually an internal error? (are those
"this-should-never-happen" situations that are not expected?
Yep.
A real exception is an exception within the VM that can be caught by user
programs (right?).
Yes.
... What sho
Adam Thomason <[EMAIL PROTECTED]> wrote:
> Sometime recently the 'testexec' Makefile target stopped working.
> Removing the offending line has no impact that I can see on the test
> suite (test, testj, or testP), so the attached patch removes it
Thanks, applied.
leo
Joshua Gatcomb <[EMAIL PROTECTED]> wrote:
> After the change - case 3 now prints thread 1.
Strange.
> You mentioned in the previous email that you were
> interested in knowing if this was Windows IO or the
> Cygwin variant. I would love to give you that
> information, but color me clueless.
S/
--- Leopold Toetsch
<[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Leopold Toetsch
> # Please include the string: [perl #31785]
> # in the subject line of all future correspondence
> about this issue.
> #
http://rt.perl.org:80/rt3/Ticket/Display.html?id=31785
> >
>
>
> $ perl tools/de
Jens Rieks <[EMAIL PROTECTED]> wrote:
> On Friday 01 October 2004 08:42, Leopold Toetsch wrote:
>> > sucks a lot less than making python programmers say
>> > "import Foo.ns.Bar.scalar.baz"
>>
>> And that's not possible because CPython, JPython, IronPython, ...
>> wouldn't execute it.
> Yes, but tho
--- Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Joshua Gatcomb <[EMAIL PROTECTED]> wrote:
> > ... only 1 of the
> > two messages is displayed
>
> I've fixed a flaw in the IO flush code. Please try
> again, thanks.
Still not working, but thanks! The behavior has
changed a bit though.
Here is t
# New Ticket Created by Jens Rieks
# Please include the string: [perl #31789]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31789 >
---
osname= openbsd
osvers= 3.5
arch= i386-openbsd
cc= cc
---
Flags:
category
Kj <[EMAIL PROTECTED]> wrote:
> But what is actually an internal error? (are those
> "this-should-never-happen" situations that are not expected?
Yep.
> A real exception is an exception within the VM that can be caught by user
> programs (right?).
Yes.
> ... What should happen with an internal
On Friday 01 October 2004 08:42, Leopold Toetsch wrote:
> > sucks a lot less than making python programmers say
> > "import Foo.ns.Bar.scalar.baz"
>
> And that's not possible because CPython, JPython, IronPython, ...
> wouldn't execute it.
Yes, but those Pythons will not execute such a program at a
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #31786]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31786 >
When going from a build with --optimize to one w/o and doing make, not
all Parrot
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #31785]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31785 >
$ perl tools/dev/parrotbench.pl
Can't locate Config/IniFiles.pm in @INC (...
leo
Joshua Gatcomb <[EMAIL PROTECTED]> wrote:
> I agree, but that doesn't explain why only 1 of the
> two messages is displayed to the screen when the sleep
> statement is present.
Overlooked that in the first place. So what you get is that the one *or*
the other string is displayed. That's a serious
Joshua Gatcomb <[EMAIL PROTECTED]> wrote:
> ... only 1 of the
> two messages is displayed
I've fixed a flaw in the IO flush code. Please try again, thanks.
leo
TOGoS <[EMAIL PROTECTED]> wrote:
> ... Otherwise your python programmer has
> to say import lib."$foo" or some such.
There is no such language syntax in Python. You just have bare words as
names - nothing else, especially no strings where you could place the
sigil.
> ... and
> sucks a lot less t
Leopold Toetsch wrote:
Kj <[EMAIL PROTECTED]> wrote:
Hello,
Just wondering (again), in order to be able to follow discussion on matters:
What is the difference between an "internal" exception and a "real"
exception (as if the
first one isn't a real exception...).
The interna
Michel Pelletier <[EMAIL PROTECTED]> wrote:
> On Thu, 2004-09-30 at 01:10, Leopold Toetsch wrote:
>>
>> Should it go into CVS abd being included in 0.1.1?
> If no one else has any objection that would be fine by me, it would
> encourage more people to try it out.
Ok.
> ... I presume I would upda
Thomas Seiler <[EMAIL PROTECTED]> wrote:
> For those languages that support native Hashes, it should be relatively
> simple to give the user direct access to a Namespace PMC as if it would
> be a native Hash, (all it needs is a Hash-vtable, maybe a Namespace PMC
> should be just a Hash)...
Well,
21 matches
Mail list logo
