On 10/19/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> My bash deletes to whitespace on ^W, so all directory levels are
> munched in a single go. Fish does stop at '/', which I would have
> thought was what you wanted. I'm sure I'm missing something here, but
> I have no clue what it is.
Hm,
I'm sure I'm missing something here, but I have no clue what it is. It may be your LOCALE or LANG; if you’re lucky, the word-breaking is locale-dependent.-Ben-
Using Tomcat but need to do more? Need to support web services, sec
On 10/20/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> On 10/12/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> [rearranged]
> > I have once again edited the relevant function, when moving/deleting
> > to the left, the boundary character should never be deleted/moved
> > past. But I am beginni
On 10/12/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
[rearranged]
> I have once again edited the relevant function, when moving/deleting
> to the left, the boundary character should never be deleted/moved
> past. But I am beginning to see a very clear trend that whenever you
> unbreak one aspe
On 10/18/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> hmm, i think it might make sense to have fish never try to reconnect to
> fishd if it fails in the beginning. (as opposed to intermediate failures)
> then the confusion would not arise. the feature would simply not exist.
>
> this would make ru
On 10/18/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 18, 2006 at 06:49:51PM +0200, Axel Liljencrantz wrote:
> > Ok, there is yet another attempted fix in the darcs tree.
>
> that does it. fishd is running again!
_Very_ happy to hear it. Thanks for sticking it out.
>
> > Hope you'll
On 10/18/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> On 10/18/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > Ok, there is yet another attempted fix in the darcs tree.
> [...]
>
> The patch works for me!! :^) WOOT! Hooray for Axel.
Yes! At last. Thank you for the help. :-D
>
> You do h
On Wed, Oct 18, 2006 at 06:49:51PM +0200, Axel Liljencrantz wrote:
> Ok, there is yet another attempted fix in the darcs tree.
that does it. fishd is running again!
> Hope you'll have the patience to try it out.
sure, that's the least i can do. since i can't really do much else
(especially now)
hmm, i think it might make sense to have fish never try to reconnect to
fishd if it fails in the beginning. (as opposed to intermediate failures)
then the confusion would not arise. the feature would simply not exist.
this would make running fishd simply optional, which might appeal to
some people
On 10/18/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> Ok, there is yet another attempted fix in the darcs tree.
[...]
The patch works for me!! :^) WOOT! Hooray for Axel.
You do have to remove 2 or 3 lines from file "env.c" before compiling.
---
On 10/17/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
[...]
> i guess from one aspect it would be nice if fish could be more robust with
> regards to working without fishd. (the only thing that should be lacking
> should be universal variables...
Very true. The problem is that fish sets the value
On 10/18/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> On 10/17/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> [...]
> > patch in the darcs tree that makes the following changes:
> >
> > * The character set of fishd, both in the fishd.HOSTNAME file and over
> > the socket, is ASCII. Non-ASCII
On 10/17/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
[...]
> patch in the darcs tree that makes the following changes:
>
> * The character set of fishd, both in the fishd.HOSTNAME file and over
> the socket, is ASCII. Non-ASCII characters and characters below 32 are
> backslash escaped.
> * If
On 10/17/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 17, 2006 at 11:30:33PM +0200, Axel Liljencrantz wrote:
> > The time was 23:16 when I begun writing this letter, I hope to manage
> > the 'today or tomorrow' with the least possible margin.
>
> more importantly, you managed to get th
On Tue, Oct 17, 2006 at 11:30:33PM +0200, Axel Liljencrantz wrote:
> The time was 23:16 when I begun writing this letter, I hope to manage
> the 'today or tomorrow' with the least possible margin.
more importantly, you managed to get this message out just minutes
before i was going to shut down f
On 10/17/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
[...]
>
> This log is very helpful. See all the 'mbrtowc' lines? That is a
> function to convert from multibyte narrow character sets to wide
> character sets. If fishd is running into errors with this, it probably
> means that there is an i
On Mon, Oct 16, 2006 at 07:19:08PM -0400, Philip Ganchev wrote:
> Did anyone else try installing the darcs version yet?
i basicly never did anything else.
greetings, martin.
--
cooperative communication with sTeam - caudium, pike, roxen and unix
offering: programming, training and admin
On Tue, Oct 17, 2006 at 12:35:48AM +0200, Axel Liljencrantz wrote:
> > > The fix for this and for the '.' crash are in
> > > the darcs tree. Hopefully, this also takes care of one of Martins
> > > bugs.
> > It does for me!!! :-)
> Great. Thanks for letting me know.
i am afraid it does not for me.
On 10/16/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> On 10/17/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> > On 10/16/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
[...]
> > j[4AܚAA�'
> > mbrtowc: Invalid or incomplete multibyte or wide character
> >
>
> This log is very helpful. See a
On 10/17/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 17, 2006 at 12:49:50AM +0200, Martin Baehr wrote:
> > i am afraid it does not for me.
> > i still get the high cpu load on fishd with the subsequent exit
>
> (argh, hit send to fast)
No problem.
> unfortunately at this point i don
On Tue, Oct 17, 2006 at 12:49:50AM +0200, Martin Baehr wrote:
> i am afraid it does not for me.
> i still get the high cpu load on fishd with the subsequent exit
(argh, hit send to fast)
unfortunately at this point i don't have any time for any debugging
other than testing new patches that you thr
On 10/17/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> On 10/16/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > On 10/16/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> > > It seems to be caused by fishd (darcs version) having trouble reading
> > > file ~/.fishd-* . If the file is removed o
On 10/16/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> On 10/16/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> > It seems to be caused by fishd (darcs version) having trouble reading
> > file ~/.fishd-* . If the file is removed or a daemon is already
> > running, Fish (either version) starts
On 10/16/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> On 10/15/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > On 10/14/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> [...]
> > > Rename all config files.
> > > Start an xterm running Bash ``xterm -e bash &``.
> > > Install released version
On 10/15/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> On 10/14/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
[...]
> > Rename all config files.
> > Start an xterm running Bash ``xterm -e bash &``.
> > Install released version 1.21.12.
> > Kill all fish and fishd instances.
> > Change to the d
On 10/14/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> On 10/13/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> >
> [...]
> > the current implementation sends fish in an endless loop when attempting
> > to delete a seperation character with ctrl-w:
>
> This is a very slippery bug.
That's not even
On Fri, Oct 13, 2006 at 11:26:27PM -0400, Philip Ganchev wrote:
> Which of the two porblems: endless loop while starting or endless loop
the starting one.
> Do you remove the released
> version and all its files, install the darcs version, and kill all
> fishd and fish instances, and you can't st
On 10/13/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
[...]
> there are some differences however, in my case i complely replaced the
> released version. so there should be no traces of it left, and i get the
> problem just within the darcs version.
Which of the two porblems: endless loop while star
On Fri, Oct 13, 2006 at 09:50:48PM -0400, Philip Ganchev wrote:
> This is a very slippery bug.
>
> It seems to be caused by a fish script, because the endless loop
> occurs only when you install the released version of fish and run any
> version of fish from the darcs directory, or install the dar
On 10/13/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
>
[...]
> the current implementation sends fish in an endless loop when attempting
> to delete a seperation character with ctrl-w:
This is a very slippery bug.
It seems to be caused by a fish script, because the endless loop
occurs only when yo
On Sat, Oct 14, 2006 at 01:13:50AM +0200, Axel Liljencrantz wrote:
> Could you try a 'darcs revert' instead?
that gives me:
$ darcs revert
hunk ./Makefile.in 173
-PROGRAMS:=fish set_color @XSEL@ @SEQ_FALLBACK@ mimedb count fish_pager
fishd
+PROGRAMS:=fish set_color @XSEL@ @
On 10/14/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 14, 2006 at 12:56:26AM +0200, Axel Liljencrantz wrote:
> > >i just ran darcs check, and that is giving me a large diff of
> > >inconsistencies.
> > Weird. A 'darcs revert' might help?
>
> the inconsistencies went away after a darcs
On Sat, Oct 14, 2006 at 12:56:26AM +0200, Axel Liljencrantz wrote:
> >i just ran darcs check, and that is giving me a large diff of
> >inconsistencies.
> Weird. A 'darcs revert' might help?
the inconsistencies went away after a darcs repair
but the problem is still there (dunno if that is any dif
On 10/14/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 14, 2006 at 12:38:31AM +0200, Axel Liljencrantz wrote:
> > I think it's strange that you are encountering two separate issues
> > that look very much like bugs I've fixed in the last few days. Maybe
> > there's something wrong with
On Sat, Oct 14, 2006 at 12:38:31AM +0200, Axel Liljencrantz wrote:
> I think it's strange that you are encountering two separate issues
> that look very much like bugs I've fixed in the last few days. Maybe
> there's something wrong with the darcs tree? What are the latest
> patches you've download
On 10/14/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> On 10/13/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> > On Fri, Oct 13, 2006 at 11:31:38PM +0200, Axel Liljencrantz wrote:
> > > > PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
> > > >6552 mbaehr25 0 3560 1512
On Sat, Oct 14, 2006 at 12:20:23AM +0200, Martin Baehr wrote:
> the fish instances are recovering.
> however, they send fishd into some loop for a while everytime i start a
> new instance.
btw, this was not the case while starting new fish instances with the old
fishd (1.21.12) (now running 1.21.
On Sat, Oct 14, 2006 at 12:17:59AM +0200, Axel Liljencrantz wrote:
> Oops... How old is the fishd version you're using?
now the latest from the repository.
> (Keep in mind the fishd version that is started will come
> from the latest _installed_ fish version, not the latest fish version
> you com
On 10/14/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 14, 2006 at 12:05:53AM +0200, Axel Liljencrantz wrote:
> > Yes, 'kill %fishd' will cause fishd to respawn at once.
>
> yup.
> but none of the running (or even new) fish instances can connect to it.
> as now fishd runs in an endless
On Sat, Oct 14, 2006 at 12:05:53AM +0200, Axel Liljencrantz wrote:
> Yes, 'kill %fishd' will cause fishd to respawn at once.
yup.
but none of the running (or even new) fish instances can connect to it.
as now fishd runs in an endless loop
i am a dead fish now ;-|
greetings, martin.
--
cooperat
On 10/13/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 13, 2006 at 11:31:38PM +0200, Axel Liljencrantz wrote:
> > > PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
> > >6552 mbaehr25 0 3560 1512 1168 R 95.1 0.3 0:07.68 fish
> >
> > Can't reproduce this, I'm
On Fri, Oct 13, 2006 at 11:31:38PM +0200, Axel Liljencrantz wrote:
> > PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
> >6552 mbaehr25 0 3560 1512 1168 R 95.1 0.3 0:07.68 fish
>
> Can't reproduce this, I'm afraid. Are you using the latest darcs
> version? I caused and
On 10/13/06, Martin Baehr <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 12, 2006 at 06:22:58PM +0200, Axel Liljencrantz wrote:
> > I will not consider future suggestions for this function unless
> > they contain a decent analysis of common usecases as well as a patch
> > to the move_word function to imp
On Thu, Oct 12, 2006 at 06:22:58PM +0200, Axel Liljencrantz wrote:
> I will not consider future suggestions for this function unless
> they contain a decent analysis of common usecases as well as a patch
> to the move_word function to implement the suggested behaviour. Sorry.
i am afraid you will
On 10/6/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> The good news is that Gmail again works with SourceForge!
>
> On 8/31/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > On 8/31/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> > > On 8/30/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> >
The good news is that Gmail again works with SourceForge!
On 8/31/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> On 8/31/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> > On 8/30/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > > On 8/27/06, Martin Bähr <[EMAIL PROTECTED]> wrote:
> > > >
On Thu, Aug 31, 2006 at 03:27:55AM -0400, Philip Ganchev wrote:
> This rule sounds complicated. I'm concerned that a user who tries to
> "discover" word deletion in Fish (without reading documentation) would
> not get the rule and would avoid deleting whole words.
the rule is in the code, the use
On 8/31/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> On 8/30/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > On 8/27/06, Martin Bähr <[EMAIL PROTECTED]> wrote:
> > > On Sun, Aug 27, 2006 at 05:36:21PM +0200, Axel Liljencrantz wrote:
> [rearranged]
>
> > Move left/right until we encounter a
On 8/30/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> On 8/27/06, Martin Bähr <[EMAIL PROTECTED]> wrote:
> > On Sun, Aug 27, 2006 at 05:36:21PM +0200, Axel Liljencrantz wrote:
[rearranged]
> Move left/right until we encounter a non-whitespace character.
> Move left/right until we encounter a
On Thu, Aug 31, 2006 at 02:47:05AM +0200, Axel Liljencrantz wrote:
> Move left/right until we encounter a non-whitespace character.
> Move left/right until we encounter a non-alphanumeric character.
> If the character we stopped on is non-whitespace, move along one more
> character.
> Patch is in
On 8/27/06, Martin Bähr <[EMAIL PROTECTED]> wrote:
> On Sun, Aug 27, 2006 at 05:36:21PM +0200, Axel Liljencrantz wrote:
> > My interpretatin of your suggestion is that there should be two levels
> > of boundaries, one with whitespace and one with other boundary
> > characters, and that they be trea
On Sun, Aug 27, 2006 at 05:36:21PM +0200, Axel Liljencrantz wrote:
> A simpler rule, that will most of the time do what you propose would
> be to only lump together a series of _identical_ boundary token. E.g.
> ' ' is a single boundary, but ' ~. ./' is 6 boundaries.
this would also help cases
On Sun, Aug 27, 2006 at 05:36:21PM +0200, Axel Liljencrantz wrote:
> My interpretatin of your suggestion is that there should be two levels
> of boundaries, one with whitespace and one with other boundary
> characters, and that they be treated differently.
that may be a sideffect yes.
the main pr
On 8/27/06, Martin Bähr <[EMAIL PROTECTED]> wrote:
> On Sun, Aug 27, 2006 at 04:53:05PM +0200, Axel Liljencrantz wrote:
> > >however this now seems to ignore whitespace as a boundary which is
> > >rather odd...
> > No? Works for me.
> >
> > Can you give a more exact description of when this happens
On Sun, Aug 27, 2006 at 04:53:05PM +0200, Axel Liljencrantz wrote:
> >however this now seems to ignore whitespace as a boundary which is
> >rather odd...
> No? Works for me.
>
> Can you give a more exact description of when this happens? What
> string do you use, and what boundaries are ignored, s
On 8/27/06, Martin Bähr <[EMAIL PROTECTED]> wrote:
> hi,
>
> ctrl-w uses a lot more characters as a word boundary, which is something
> i have always wished for but was to lazy to figure out how to do with
> bash.
> however this now seems to ignore whitespace as a boundary which is
> rather odd...
hi,
ctrl-w uses a lot more characters as a word boundary, which is something
i have always wished for but was to lazy to figure out how to do with
bash.
however this now seems to ignore whitespace as a boundary which is
rather odd...
greetings, martin.
--
cooperative communication with sTeam
57 matches
Mail list logo
