Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add option to treat text with whitespace as a signle unit #10

Open
rickysarraf opened this issue Sep 5, 2024 · 0 comments
Open

add option to treat text with whitespace as a signle unit #10

rickysarraf opened this issue Sep 5, 2024 · 0 comments

Comments

@rickysarraf
Copy link

rickysarraf commented Sep 5, 2024

Description

Currently, we can do:

@ echo 'Ritesh Raj Sarraf'
Ritesh Raj Sarraf

⛢ 19:51:01 rrs@xps ~                                                                            
@ echo Ritesh                                                                                   

ॐ 19:51:23 rrs@xps ~                                                                            
@ echo Alt+F  'Ritesh                                                                                  

Above, items are broken down by space.

The above doesn't well fit in the use case below:

♅ 19:51:32 rrs@xps ~  
@ echo "abc" > "/tmp/Ritesh Raj Sarraf.txt"

⛢ 19:52:06 rrs@xps ~  
@ cat '/tmp/Ritesh Raj Sarraf.txt'
abc

♅ 19:52:17 rrs@xps ~  
@ cat ALT+F  '/tmp/Ritesh

It only gives broken down items. That isn't useful in the filename use case.

Below is what is stored in history.

 __xonsh__.history[-1]
HistoryEntry(cmd="ls '/tmp/Ritesh Raj Sarraf.txt'", out="'/tmp/Ritesh Raj Sarraf.txt'\n", rtn=0, ts=[1725546326.3570676, 1725546326.4170177], cwd='/home/rrs')

So I was wondering if we could have an option for output_search to not split on the basis of space. Maybe \n could be a split criteria ?

@rickysarraf rickysarraf changed the title add option to treat test with space as one add option to treat text with whitespace as a signle unit Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant