We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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 ?
output_search
\n
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
Currently, we can do:
Above, items are broken down by space.
The above doesn't well fit in the use case below:
It only gives broken down items. That isn't useful in the filename use case.
Below is what is stored in history.
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 ?The text was updated successfully, but these errors were encountered: