3 ms·
This is a very informative thread for people trying to streamline their daily shell experience. I'm looking forward to experimenting with the utilities mention
by ttomaino 13y ago
This is a very informative thread for people trying to streamline their daily shell experience. I'm looking forward to experimenting with the utilities mentioned here. I spend a significant amount of time in, and moving between CVS sandboxes. All my sandboxes have the same internal directory structure, but the root of the path changes. To speed up navigation time I created a tool to replace directory names with aliases. The aliases are persistent. They can also be "stacked", which allows you to specify a sandbox as an alias, then reuse your existing aliases to navigate within the sandbox. Auto-completion in the shell is an excellent companion as well. More information on "stacked.aliases", as well as the source can be found here: https://github.com/ttomaino/stacked_aliases/wiki https://github.com/ttomaino/stacked_aliases/wiki. I include one example to illustrate:
As an example, the following two sandboxes contain the Broadcom Ethernet driver:
/build/username/sandbox_a/software/vendors/linux/linux-2.6.35.7/drivers/ethernet/broadcom
/build/username/sandbox_b/software/vendors/linux/linux-2.6.35.7/drivers/ethernet/broadcom
Use the add alias command aa <alias name> <directory> to create aliases for the sandboxes:
aa a /build/username/sandbox_a
aa b /build/username/sandbox_b
Then create an alias for the Broadcom directory:
aa brcm software/vendors/linux/linux-2.6.35.7/drivers/ethernet/broadcom
To change to the Broadcom directory in sandbox_a, just stack the appropriate aliases using the ua command. Stacking is done by stringing the aliases together with a period delimiter:
ua a.brcm
To change to the Broadcom directory in sandbox_b:
ua b.brcm