|
|
you can open files with apps this way, too:
"
Mail.app This.file" will open Mail, create a new message and attache "This.file".
should anybody wonder, why i left the *.app extension at the links: this way you can say the difference between GUI-apps and command.
i realized that this is nescessary when i discovered that shell commands aren't case-sensitive [sic!]. at least when they refer to a commandlinetool from the filesystem. not that surprising on a case-insensitive filesystem. aliases from .bashrc are still case-sensitive, btw. (has this been like this before tiger?) anyway, because of that (and /usr/bin beiing in $PATH before ~/Apps) " Mail" had launched /usr/bin/mail rather than Mail.app.
you can open files with apps this way, too:
Tab completion also works case-sensitive. So for me, Mai[Tab], only generates Mail.app, whereas mai[Tab] only generates mail. Interesting how case sensitivity is mixed. I'm anxious for the day when a larger majority of Mac apps support the Mac OS X Extended (journaled, case-sensitive) file system.
you can open files with apps this way, too:
Actually, the filesystem is not case-sensitive. Only case-preserving.
you can open files with apps this way, too:
"I'm anxious for the day when a larger majority of Mac apps support the Mac OS X Extended (journaled, case-sensitive) file system."Then: "Actually, the filesystem is not case-sensitive. Only case-preserving. An annoying difference."Guess you either didn't read closely enough, or weren't aware, but 10.4 has a case-sensitive version of HFS+J. It's called HFSX. So actually, the filesystem that's referred to by the original poster is case-sensitive.
you can open files with apps this way, too:
If you create the links in the article with all lowercase names then the tab completion will work with lower case.
I have a bash completion fragment that you can put in say ~/.bash_completion or save it to ~/open_completion and source it using the command:
. open_completion
that handles this in a text file rather than a bunch of links. The mdfind command was from another comment. Use "grep -i" instead of grep to make the completion case insensitive.
bash completion
Ummmm the script didn't come out quite right. How do you get backslashes? I've forgotten. Anyway here is a link to text version. The spaces are escaped properly as well.
|
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|