Don McLane | 11 Jun 03:44 2006

Re: wily in cygwin

quanstro <at> quanstro.net wrote:
> On Wed Jun  7 23:13:44 CDT 2006, dmclane <at> u.washington.edu wrote:
>> I just started using Wily and had some questions/comments.  I'm running 
>> it in cygwin (which is probably the source of my problems).
>>
>> Is it supposed to display "$PWD" in the tag?  Seems like that's an 
>> expression that should be evaluated somehow.
>>
> 
> you need to kill the PWD environment variable; e.g.
> 	bash$ PWD= wily
> although i noticed that wily is fooled by variables with values like ".".
> 

Yes, I can get rid of the "$PWD" in the tag if I start wily like that 
... but, opps, now I have to change $HOME too.  And who knows what else. 
  Is this really a feature?

[snip]
>> Shouldn't I be able to right-click on "../" and open a window in the 
>> parent directory?
> 
> you should.
> 

I seem to have a talent for being in the wrong place, at the wrong time, 
with the wrong assumptions.  It's a cygwin thing.  I happened to be in 
the cygwin root, "/", but knew that I was really in "C:/cygwin" and 
expected that right clicking would jump up to "C:".  Well it doesn't do 
that in the cygwin shell either (you have to go to "/cygdrive/c" to get 
(Continue reading)

Don McLane | 8 Jun 06:13 2006

wily in cygwin

I just started using Wily and had some questions/comments.  I'm running 
it in cygwin (which is probably the source of my problems).

Is it supposed to display "$PWD" in the tag?  Seems like that's an 
expression that should be evaluated somehow.

If you have a file named "new" (lowercase n) and you middle-click "New" 
then it opens the file "new".  What are the odds that a new user, trying 
wily for the first time, had a file named "new"?  Well it happened!  It 
makes for a very confused newbie.

Shouldn't I be able to right-click on "../" and open a window in the 
parent directory?

Anyway, thanks to the developers.  Wily promises to be a really 
productive environment.

Don

ozan s yigit | 6 Apr 22:59 2006
Picon

one more thing: config

i should mention that while i upgraded config bits in wily
i did not try to clean it up; any input from autoconf/libtool
et al. experts would be welcomed. [i detest autoconf & friends
but i doubt a replacement is coming anytime soon...]

oz

ozan s yigit | 6 Apr 21:24 2006
Picon

wily 0.13.42

it lives. :)

new wily version. updated ftp://ftp.cs.yorku.ca/pub/wily/src/
and will update sourceforge later tonight.

9libs had to have a micro-version increment. it is now at 1.0.1.

These are all the interesting changes from wily 0.13.41 to
0.13.42 done by tommy Pettersson <ptp <at> lysator.liu.se>. Please
let me know if you run into trouble with any of these changes.
if you have a philosophical disagreement with any of the fixes
also let me know, and i will try to resolve it. 

thank you tommy. and thanks to derek peschel for bugging me
about configs. thank you to all those who have sent fixes in
the past, some of which is in this new version. i appreciate
the help. 

---- changes ---

Configs for 9libs and wily-9libs have been brought up-to-date
to allow 9libs compilation under Mac OS-X.

The most complicated change is with reading utf8. Multibyte utf
sequences could get split and generate two invalid runes instead
of one valid. This could happen both on file reads, if the file
was larger then the temporary read buffer, and on output events
from external processes. Wily sometimes missed to warn about
nulls when reading large files. Nulls are now replaced with
invalid runes on file reads. Wily will also warn about both
(Continue reading)

ozan s yigit | 23 Sep 17:13 2005
Picon

Re: Put Put.lhs

tommy, sure, thanks for the offer.
i will take a patch release and replace the current
versions in sourceforge and elsewhere. [gee, i thought
everyone had switched to acme and forgotten about wily...]

oz
---
oz <at> cs.yorku.ca
http://blogs.sun.com/plan9

 > I was editing a file named Put.lhs when I found a cute but
> rather annoying bug in wily.  :-)
> 
> I'll probably fix it when I get time.
> 
> I have a couple of bugfixes I have not sent to the list yet,
> including one for 'write way out of buffer' responsible for
> a heap of weird core dumps.
> 
> With all my bugfixes in place I have been running the same
> wily invocation for months without crashes.  That is more
> than can be said about the "latest" wily release.  If nothing
> else, just a new minor release with only these bugfixes,
> no drum rolls and press statements needed, would be a very
> good thing for anyone using or wanting to use wily.  I can
> offer to prepare and tar up such a release (both main and
> 9lib branches), with a changelog, if it will be accepted.
> 
> 
> -- 
(Continue reading)

Tommy Pettersson | 23 Sep 16:25 2005
Picon
Picon
Picon

Put Put.lhs

I was editing a file named Put.lhs when I found a cute but
rather annoying bug in wily.  :-)

I'll probably fix it when I get time.

I have a couple of bugfixes I have not sent to the list yet,
including one for 'write way out of buffer' responsible for
a heap of weird core dumps.

With all my bugfixes in place I have been running the same
wily invocation for months without crashes.  That is more
than can be said about the "latest" wily release.  If nothing
else, just a new minor release with only these bugfixes,
no drum rolls and press statements needed, would be a very
good thing for anyone using or wanting to use wily.  I can
offer to prepare and tar up such a release (both main and
9lib branches), with a changelog, if it will be accepted.

--

-- 
Tommy Pettersson <ptp <at> lysator.liu.se>

Tommy Pettersson | 4 Mar 03:59 2005
Picon
Picon
Picon

nicified autobackup (multiple timers in 9libs)

Hello again,

I have made 9libs (or rather libXg) support multiple timers.
It was pretty clean.  This makes my autosave creature sooo
much cleaner, without the horrific global timer to turn off
and on all the time.

If anyone wants to see these patches (multiple timers or new
improved autosave) on the list or in private, just shout.
I don't want to overrun my patch quote to the list.  ;-)

--

-- 
Tommy Pettersson <ptp <at> lysator.liu.se>

Tommy Pettersson | 4 Mar 03:42 2005
Picon
Picon
Picon

fix for big bug, trashed multi-byte utf

Hello,

I have fixed a rather serious bug in wily, but first some
small ones.  (patches agains wily-0.13.41-9libs)

If you enter a rune with hex value 0000 (zero) with M-X, 9libs
barfs on stderr and wily starts acting goofy.  I thought a
while about what to do about this, and I think it should be
regarded as a deliberate action from the user.  Wily can't
have rune zero in the buffer, but it can represent an error
rune, so I made it insert a such.  This has the advantage
that you can enter an error rune in the tag to search for it
in a large text with B3.  I did this a lot when fixing the
bib bug coming later.

diff -rN -u old-diff/wily-9libs/wily/keyboard.c new-diff/wily-9libs/wily/keyboard.c
--- old-diff/wily-9libs/wily/keyboard.c	Fri Mar  4 02:07:39 2005
+++ new-diff/wily-9libs/wily/keyboard.c	Fri Mar  4 01:56:42 2005
 <at>  <at>  -16,6 +16,8  <at>  <at> 
 void
 dokeyboard(View *v, Rune r) {
 	switch(r) {
+	case 0:			addrune(v,Runeerror); break;
+
 	case DownArrow:
 	case UpArrow:
 	case Home:

Here's a rendering bug.  Put the cursor towards the end of a
long text.  Do 'Get short-file' in the tag.  Wily will reuse
(Continue reading)

Sam Holden | 3 Mar 23:27 2005
Picon
Picon

An email about wily rather than spam

I've just started working trying to get my head around a reasonably large
chunk of python code. And finally got the three button usb mouse to play 
nice with my laptop so I'm using wily to help.

So I'm hoping there's a python programmer somewhere round these parts
who can tell me I'm dumb and should do X, Y, and Z.

I use my own pure-python interface to wily's mesage interface which 
I mentioned here before, it's similar enough to the standard python
wrapper around the C lib...

Anyway I found BicycleRepairMan which seems unmaintained, lacking in
features, and buggy, but it does do a couple of things that seem
useful. It's written with IDE integration in mind so I'm integrating
it with wily. The annoyance is that it assumes a line/column approach
to files which wily just doesn't have.

Anyway, enough with the ranting and on to a code snippet, to find the
definition of something that is selected you middle click a command
which executes:

---start code---
#!/usr/bin/python
import os
import wily
import bike

def get_name_line_column(filename=None):
    if filename is None:
        filename = os.getenv('WILYPATH')
(Continue reading)

Bill Trost | 31 Jan 04:27 2005

wilyfans feature: RSS feeds

I'm not a big RSS fan myself (OK, so I've never used it), but I can see
this might be useful. Anyone working on a wily RSS client?

Bill

From: John Madden <weez <at> freelists.org>
Subject: [Freelists News] RSS archive feeds now available
Date: 2005-01-30 03:17:28 GMT
===
- The FreeLists Newsletter -
 You're receiving this email because you are subscribed
 to the FreeLists Newsletter, a newsletter sent out to all 
 FreeLists list owners.  It contains important updates about 
 changes to FreeLists services.  For subscription information, 
 please see the bottom of this email.
 Administrative contact: weez <at> freelists.org
===

We made a new feature available today: syndication of all mailing lists via 
RSS feeds.  Visitors to the archives can track a list without having to be 
subscribed and without having to watch the archives manually.  RSS is popular 
in the Blog space, but it's quite useful and is popping up just about 
everywhere.

(Continue reading)

Tommy Pettersson | 27 Jan 18:59 2005
Picon
Picon
Picon

small bugfixes for wily-0.13.41-9libs

Here are some bugfixes for wily-0.13.41-9libs.

The function prototype for rpc_freehandle() has the wrong
name in the header file.

diff -rN -u diff-old/wily-9libs/include/msg.h diff-new-1/wily-9libs/include/msg.h
--- diff-old/wily-9libs/include/msg.h	Thu Jan 27 17:37:26 2005
+++ diff-new-1/wily-9libs/include/msg.h	Thu Jan 27 17:35:27 2005
 <at>  <at>  -87,7 +87,7  <at>  <at> 
 Handle*	rpc_init		(int);
 int		rpc_fileno(Handle *h);
 Bool		rpc_isconnected(Handle*);
-void		rpc_free (Handle*);
+void		rpc_freehandle (Handle*);

 char*	rpc_list		(Handle*h, char **bufptr);
 char*	rpc_new		(Handle*, char *, Id*, ushort);

This one has already been reported to the list by Elliott
Hughes; errno should be set to 0 before call to diag().

diff -rN -u diff-old/wily-9libs/wily/event.c diff-new-1/wily-9libs/wily/event.c
--- diff-old/wily-9libs/wily/event.c	Thu Jan 27 17:37:26 2005
+++ diff-new-1/wily-9libs/wily/event.c	Thu Jan 27 17:35:27 2005
 <at>  <at>  -168,6 +168,7  <at>  <at> 
 kill_list(void){
 	Key	*k;
 	
+	errno = 0;
 	for(k = keytab; k < keytab + MAXKEYS; k++)
(Continue reading)


Gmane