You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sack -sd ~/some/other/ ~/bar/foo/ and other variants is not possible, although there is a mention or two of directory(s) in the script.
This -i-s- possible admittedly a ~/some/other/ is set and then doing "prompt$ sack foo ~/bar/foo/" will search and spit both the results in the preset in profile AND the command added directory.
The above way one has sack now searching the profile announced directory AND the command line hinted directory.
Question: how to set reliably multiple directories in a profile, since I am using ag and not ack, is ag the culprit?
The additional reason is that the results cannot be called up from another terminal for the directory added to the command, sack script switches to the profile declared directory only to act upon "F #"
Logically there is no way of knowing for the script what the command line given directory is.
Regards, the added possibility to jump from a different terminal to a search result and open the editor, is an appreciated time and focus gain. This way, is also cleaner then within vim doing the search, one is not always within the editor, and the quickview of vim has not the real estate of the terminal window.
The text was updated successfully, but these errors were encountered:
sack -sd ~/some/other/ ~/bar/foo/ and other variants is not possible, although there is a mention or two of directory(s) in the script.
This -i-s- possible admittedly a ~/some/other/ is set and then doing "prompt$ sack foo ~/bar/foo/" will search and spit both the results in the preset in profile AND the command added directory.
The above way one has sack now searching the profile announced directory AND the command line hinted directory.
Question: how to set reliably multiple directories in a profile, since I am using ag and not ack, is ag the culprit?
The additional reason is that the results cannot be called up from another terminal for the directory added to the command, sack script switches to the profile declared directory only to act upon "F #"
Logically there is no way of knowing for the script what the command line given directory is.
Regards, the added possibility to jump from a different terminal to a search result and open the editor, is an appreciated time and focus gain. This way, is also cleaner then within vim doing the search, one is not always within the editor, and the quickview of vim has not the real estate of the terminal window.
The text was updated successfully, but these errors were encountered: