headers
Don McLane | 11 Jun 2006 03:44

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)

Permalink | Reply | 1 comment |
headers
Don McLane | 8 Jun 2006 06:13

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
Permalink | Reply | 2 comments |
headers
quanstro | 7 Apr 2006 15:34
Favicon

Re: one more thing: config

does wily really need autoconf?

what non-portable functions does will use.  if there are any, could they be eliminated?

- erik

> -----Original Message-----
> From: ozan s yigit [mailto:oz <at> cs.yorku.ca]
> Sent: Thursday, April 6, 2006 08:59 PM
> To: wilyfans <at> freelists.org
> Subject: 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
> 
>
Permalink | Reply | 0 comments |
headers
ozan s yigit | 6 Apr 2006 22:59
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
Permalink | Reply | 0 comments |
headers
ozan s yigit | 6 Apr 2006 21:24
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)

Permalink | Reply | 4 comments |
headers
ozan s yigit | 23 Sep 2005 17:13
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)

Permalink | Reply | 1 comment |
headers
Steve Kilbane | 29 Sep 2004 22:25
Picon
Picon

Re: How to develope wily?

Tommy wrote:
> Files with a `:' in their name doesn't work with B3.
> I want to try and fix this.  I have a lot of such files in
> my maildir-formated mail directories.

It's been a _long_ time since I wrote any Wily client code,
so I forget the precise semantics of B3 clicks (specifically,
whether the client receives the event with the expanded
string), but I do wonder whether you could "fix" this case
with a client that presented your maildir directories in a
usable manner, just as mbox files and newgroups can be
represented as directories.

steve
Permalink | Reply | 1 comment |
headers
ozan s yigit | 29 Sep 2004 18:46
Picon

Re: How to develope wily?

hi tommy:

> I am thinking about maybe hacking a little on wily (and its
> supporting libraries).  There are some things I want to try
> and change or improve (to my taste).  I figure at least some
> of it may be stuff that other wily users want too.
> 
> Is there some sort of master plan for wily's future
> development?  I have skimmed through the latest five or so
> years of mails on this list, but I couldn't find out if there
> is active development going on right now and if there is a
> development version of wily somewhere.  I assume this list
> is where to coordinate development.  So shout if you think
> any of the following is stupid or could be done in a way that
> better suits you/others.

there is really no master plan for the current wily. there are
a few acme compatibility glitches and font issues that should be
addressed. yes there has been some spotty unreleased development
on it. i got distracted for a while with a derivative that is now
abandoned. if you have enhancements that you feel the community
(such as it is :) would want, we can discuss that. i still owe
everyone a fully-patched next version.

> What lib: I understand that the old (pre-lib9) libraries
> in the latest "official" wily-0.13.41 are being obsoleted.
> And wily is not (yet?) ported to the new libdraw &al that
> came with the porting of acme to unix, right, so it will
> not be a total waste if I happen to make some improvements
> to lib9?  Or should I definitely be helping in porting wily
(Continue reading)

Permalink | Reply | 1 comment |
headers
Tommy Pettersson | 23 Sep 2005 16:25
Picon
Picon
Picon
Favicon

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>
Permalink | Reply | 0 comments |
headers
Tommy Pettersson | 4 Mar 2005 03:59
Picon
Picon
Picon
Favicon

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>
Permalink | Reply | 0 comments |
headers
Tommy Pettersson | 4 Mar 2005 03:42
Picon
Picon
Picon
Favicon

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)

Permalink | Reply | 0 comments |

Gmane