.* expansion

Hi fishers,

I've noticed that it is very uncomfortable to use wild cards to work with  
'hidden' files and folders, because when expanded it always produces '.'  
and '..' directories, which normally are almost never needed for expansion.

Consider the following example: you need to copy all the files and  
directories (including hidden) from one directory to another. You can not  
write
cp -r dir/* dir/.* destination/
or
cp -r dir/{,.}* destination/

because it will be also expanded to the dir/.., which means that cp will  
copy also the contents of the outer directory. I've failed to find an  
example, where you really need these '.' and '..' in expansion. Does  
anyone knows them?

So I propose to remove '.' and '..' from '.*' expansion. If someone need  
them, he can add them manually with with {} syntax.

regards,
Maxim

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Re: .* expansion

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Fish-users mailing list
Fish-users@...
https://lists.sourceforge.net/lists/listinfo/fish-users

Re: .* expansion

Dave, do you want to say that your fish can expand character classes?
Like [a-zA-Z]?
Mine can not (:

On Tue, 08 May 2012 22:07:56 +0400, David Frascone <dave@...>  
wrote:

> That looks good.
>
> I usually just do .[a-zA-Z]*
>
> :)
>
> On Fri, May 4, 2012 at 2:41 AM, Maxim Gonchar <gmaxfl@...> wrote:
>
>> Hi fishers,
>>
>> I've noticed that it is very uncomfortable to use wild cards to work  
>> with
>> 'hidden' files and folders, because when expanded it always produces '.'
>> and '..' directories, which normally are almost never needed for  
>> expansion.
>>
>> Consider the following example: you need to copy all the files and
>> directories (including hidden) from one directory to another. You can  
>> not
>> write
>> cp -r dir/* dir/.* destination/
>> or
>> cp -r dir/{,.}* destination/
>>
>> because it will be also expanded to the dir/.., which means that cp will
>> copy also the contents of the outer directory. I've failed to find an
>> example, where you really need these '.' and '..' in expansion. Does
>> anyone knows them?
>>
>> So I propose to remove '.' and '..' from '.*' expansion. If someone need
>> them, he can add them manually with with {} syntax.
>>
>> regards,
>> Maxim
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.  
>> Discussions
>> will include endpoint security, mobile security and the latest in  
>> malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Fish-users mailing list
>> Fish-users@...
>> https://lists.sourceforge.net/lists/listinfo/fish-users

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Re: .* expansion

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Fish-users mailing list
Fish-users@...
https://lists.sourceforge.net/lists/listinfo/fish-users

Announcing Open Beta for our fancy new fish fork

Hello fellow fish fans! I am ridiculous_fish, and I come bearing lungfuls of new life!

Over the past year, I and my partner Siteshwar have been working on a fish fork. We've been modernizing
fish's codebase, while adding some truly compelling features and improving performance. We've been
living on this fork for months, and we think it's _awesome_. Compared to stock fish, our branch is
noticeably faster and easier to maintain, and its new features have ruined me for all other shells. bash
now tastes like cardboard.

Our fork is now in Open Beta, and we'd like to invite you to try it out! We are interested in feedback and bug reports.

We'd also like to start a discussion about our changes and whether/how to incorporate them into fish trunk
(which we would very much like to do). Our changes are transformative and impact nearly every aspect of
fish's code base, so it is not to be undertaken lightly. But our changes are also very compelling from the
perspectives of both users and maintainers, and our months of living-on have given us a lot of confidence
in them. Our branch is not only the best fish ever made; we think it's the best POSIX command line shell, period.

Here's how to get it!

  Main page: http://ridiculousfish.com/shell/
  Open beta page: http://ridiculousfish.com/shell/beta.html
  Release notes: http://ridiculousfish.com/shell/release_notes.html
  Gitorious page: https://gitorious.org/~ridiculousfish/fish-shell/fishfish

The relevant git branch is fish_fish.

Please share your thoughts, reactions, rants, raves, and bug reports on this list. If all goes well, we'll
announce the Open Beta more widely in the upcoming week.

A few teaser improvements (for a longer list, see the Release Notes above):

- Autosuggestions (think URL fields in browsers)
- 256 color support
- Web-based configuration
- Syntax highlighting is now multithreaded, so it doesn't cause stuttering typing on slow disks / filesystems
- Overall performance is way better
- It's all in (sane) C++. No more string_buffer_t, array_list_t, or hash_table_t, and no more halloc!

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Re: Announcing Open Beta for our fancy new fish fork

On Wed, May 30, 2012 at 02:43:57AM -0700, ridiculous_fish wrote:
> - It's all in (sane) C++. No more string_buffer_t, array_list_t, or hash_table_t, and no more halloc!

so it's more like a rewrite than a fork?

greetings, martin.
--

-- 
cooperative communication with sTeam      -     caudium, pike, roxen and unix
services:   debugging, programming, training, linux sysadmin, web development
--
pike programmer      working in china                 societyserver.(org|net)
foresight developer  community.gotpike.org                 foresightlinux.org
unix sysadmin        (open-steam|www.caudium).org                  realss.com
Martin Bähr          http://societyserver.org/mbaehr/      

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Re: Announcing Open Beta for our fancy new fish fork

Hi ridiculous_fish,

it's a really news.

Congratulations with beta!

Maxim

On Wed, 30 May 2012 13:43:57 +0400, ridiculous_fish  
<corydoras@...> wrote:

> Hello fellow fish fans! I am ridiculous_fish, and I come bearing  
> lungfuls of new life!
>
> Over the past year, I and my partner Siteshwar have been working on a  
> fish fork. We've been modernizing fish's codebase, while adding some  
> truly compelling features and improving performance. We've been living  
> on this fork for months, and we think it's _awesome_. Compared to stock  
> fish, our branch is noticeably faster and easier to maintain, and its  
> new features have ruined me for all other shells. bash now tastes like  
> cardboard.
>
> Our fork is now in Open Beta, and we'd like to invite you to try it out!  
> We are interested in feedback and bug reports.
>
> We'd also like to start a discussion about our changes and whether/how  
> to incorporate them into fish trunk (which we would very much like to  
> do). Our changes are transformative and impact nearly every aspect of  
> fish's code base, so it is not to be undertaken lightly. But our changes  
> are also very compelling from the perspectives of both users and  
> maintainers, and our months of living-on have given us a lot of  
> confidence in them. Our branch is not only the best fish ever made; we  
> think it's the best POSIX command line shell, period.
>
> Here's how to get it!
>
>   Main page: http://ridiculousfish.com/shell/
>   Open beta page: http://ridiculousfish.com/shell/beta.html
>   Release notes: http://ridiculousfish.com/shell/release_notes.html
>   Gitorious page:  
> https://gitorious.org/~ridiculousfish/fish-shell/fishfish
>
> The relevant git branch is fish_fish.
>
> Please share your thoughts, reactions, rants, raves, and bug reports on  
> this list. If all goes well, we'll announce the Open Beta more widely in  
> the upcoming week.
>
> A few teaser improvements (for a longer list, see the Release Notes  
> above):
>
> - Autosuggestions (think URL fields in browsers)
> - 256 color support
> - Web-based configuration
> - Syntax highlighting is now multithreaded, so it doesn't cause  
> stuttering typing on slow disks / filesystems
> - Overall performance is way better
> - It's all in (sane) C++. No more string_buffer_t, array_list_t, or  
> hash_table_t, and no more halloc!
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Fish-users mailing list
> Fish-users@...
> https://lists.sourceforge.net/lists/listinfo/fish-users

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Re: Announcing Open Beta for our fancy new fish fork

Hi ridiculous_fish

This looks like it would have been a lot of work!

Thanks so much for doing this.

I am just installing it now.

I think the site is very good and I appreciate your sense of humour-Patrick

On 12-05-30 05:43 AM, ridiculous_fish wrote:
> Hello fellow fish fans! I am ridiculous_fish, and I come bearing lungfuls of new life!
>
> Over the past year, I and my partner Siteshwar have been working on a fish fork. We've been modernizing
fish's codebase, while adding some truly compelling features and improving performance. We've been
living on this fork for months, and we think it's _awesome_. Compared to stock fish, our branch is
noticeably faster and easier to maintain, and its new features have ruined me for all other shells. bash
now tastes like cardboard.
>
> Our fork is now in Open Beta, and we'd like to invite you to try it out! We are interested in feedback and bug reports.
>
> We'd also like to start a discussion about our changes and whether/how to incorporate them into fish trunk
(which we would very much like to do). Our changes are transformative and impact nearly every aspect of
fish's code base, so it is not to be undertaken lightly. But our changes are also very compelling from the
perspectives of both users and maintainers, and our months of living-on have given us a lot of confidence
in them. Our branch is not only the best fish ever made; we think it's the best POSIX command line shell, period.
>
> Here's how to get it!
>
>    Main page: http://ridiculousfish.com/shell/
>    Open beta page: http://ridiculousfish.com/shell/beta.html
>    Release notes: http://ridiculousfish.com/shell/release_notes.html
>    Gitorious page: https://gitorious.org/~ridiculousfish/fish-shell/fishfish
>
> The relevant git branch is fish_fish.
>
> Please share your thoughts, reactions, rants, raves, and bug reports on this list. If all goes well, we'll
announce the Open Beta more widely in the upcoming week.
>
> A few teaser improvements (for a longer list, see the Release Notes above):
>
> - Autosuggestions (think URL fields in browsers)
> - 256 color support
> - Web-based configuration
> - Syntax highlighting is now multithreaded, so it doesn't cause stuttering typing on slow disks / filesystems
> - Overall performance is way better
> - It's all in (sane) C++. No more string_buffer_t, array_list_t, or hash_table_t, and no more halloc!
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Fish-users mailing list
> Fish-users@...
> https://lists.sourceforge.net/lists/listinfo/fish-users
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

fish_fish

Hi,

So I'm trying new fish and have some questions and notes. It became really  
fast and amazing.

1) On archlinux default python is python3. So internalize script and  
webconfig scripts do not work out of the box, until i replace  
/usr/bin/python by /usr/bin/python2.

2) I see that I can not now execute directories. I.e. I can not use '..'  
as command to go to the upper directory.
Of course I can catch the event to handle it. But it doesn't colorize  
correct paths as green now. Is this feature completely deleted?

3) __fish_config_interactive.fish contains a command 'which -s'
I do not know what -s should mean, but my 'which' doesn't support this  
option (I've tried on arch, debian and ubuntu).
The other thing is that which outputs to the stderr if command not found.  
So it's better to use ^/dev/null redirection as well.

The problem is that 'which -s command-not-found' is also hardcoded in  
builtin_scripts.cpp, so it's not easy to understand why it keep claiming,  
even after modifying the __fish_config_interactive.fish

4) It seems that commands are interpreted even if they are not to be  
executed:
'false; and dfgsfhsfhethr' will cause an error.

That's bad, because it shows warnings if I try to test if command is valid:
type sdfsdfsdf >/dev/null; and sdfsdfsdf

5) It ignores my prompt. It seems that it ignores my functions, if they  
override functions from /usr/local/share/fish.
It ignores them, even if I delete /usr/local/share/fish from  
$fish_function_path.
I also can not edit fish functions from 'share' with funced.

6) I like the idea of autosuggestions, I feel very comfortable and natural  
with them. I would suggest to add the possibility to set a color to the  
auto-suggested part (blinking?).
Now it's the same as the other part of the command and if you loose your  
attention for a while, you think that you get the command already and you  
get an error when you try to execute it.

best regards,
Maxim

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Re: Announcing Open Beta for our fancy new fish fork

On 30 Μαϊ 2012, at 12:43 μ.μ., ridiculous_fish wrote:

> Hello fellow fish fans! I am ridiculous_fish, and I come bearing lungfuls of new life!

Have you thought on sending this build to macports?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fish-users mailing list
Fish-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users