I generally do not use the .txt extension .. presuming it to be text. This is likely a Bad Habit due to README's, shell scripts, and notes etc but seems relatively harmless.
But recently I've started using things like Dropbox and other internet facilities that really get upset about this. (BTW: I'd love a good iPad text editor .. any good ideas?) So it seems I'll have to start adding the .txt extension, sigh.
One annoyance in textmate is that this makes the tabs larger and hang off the end.
So I guess there really are two questions: - Specifically: Is there a way to have textmate not show the extensions? - Generally: Am I right that I'm doomed to .txt usage?
-- Owen
Owen Densmore wrote:
(BTW: I'd love a good iPad text editor .. any good ideas?)
While this is a touch off-topic for the list, it depends on what kind of text you're looking to edit. My favorite editor by far has been PlainText, which works with Dropbox. But as the name suggests, it's for editing plain text files -- I use it for Markdown, but it's not syntax-aware, nor is it particularly customizable. It is, however, very straightforward, readable and usable, which are the main things I ask for. Sometime this year PlainText may get a "big brother," a new incarnation of the existing iPhone editor WriteRoom, which will have more features; we'll see, I suppose.
If you're looking for a good code editor for the iPad... uh, let me know if you find one. :)
- Watts
On Jan 5, 2011, at 11:50 AM, Owen Densmore wrote:
BTW: I'd love a good iPad text editor .. any good ideas?
Don't have an iPad, but Elements supposedly supports it. I use Elements all the time on my iPhone and would definitely recommend it. Especially if you do anything with Markdown. (It can convert and display it as HTML on the fly.)
- Specifically: Is there a way to have textmate not show the extensions?
It might respect the Finder setting on this, but I haven't tried.
- Generally: Am I right that I'm doomed to .txt usage?
Until every platform agrees on a way to store metadata and every network protocol is updated to transmit that metadata along with the file, I think we're stuck using extensions.
Take a look at Textastic for iPad
On Wed, Jan 5, 2011 at 1:45 PM, Rob McBroom mailinglist0@skurfer.com wrote:
On Jan 5, 2011, at 11:50 AM, Owen Densmore wrote:
BTW: I'd love a good iPad text editor .. any good ideas?
Don't have an iPad, but Elements supposedly supports it. I use Elements all the time on my iPhone and would definitely recommend it. Especially if you do anything with Markdown. (It can convert and display it as HTML on the fly.)
- Specifically: Is there a way to have textmate not show the extensions?
It might respect the Finder setting on this, but I haven't tried.
- Generally: Am I right that I'm doomed to .txt usage?
Until every platform agrees on a way to store metadata and every network protocol is updated to transmit that metadata along with the file, I think we're stuck using extensions.
-- Rob McBroom http://www.skurfer.com/
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 2011-01-05 13:45, Rob McBroom wrote:
Until every platform agrees on a way to store metadata and every network protocol is updated to transmit that metadata along with the file, I think we're stuck using extensions.
Well, we *could* infer the file type from its actual content instead of hoping that the filename and other metadata are present and correct. The 'file' command does this pretty successfully, though it does sometimes get fooled trying to identify the specifics of text files. Many editors use a combination of content detection and file extension to figure out the file type. (That's a hint, Allan! :-)
$ file * INSTALL: ASCII English text MAINTAINERS: UTF-8 Unicode English text Makefile: ASCII make commands text README: ASCII English text config.err: ASCII c program text, with very long lines config.h: ASCII c program text config.log: ASCII c program text, with very long lines configure: POSIX shell script text executable doc: directory ffmpeg: Mach-O 64-bit executable x86_64 ffmpeg.c: ASCII c program text ffmpeg.d: ASCII text ffmpeg.o: Mach-O 64-bit object x86_64
On 5 Jan 2011, at 20:16, Steve King wrote:
[…] The 'file' command does this pretty successfully, though it does sometimes get fooled trying to identify the specifics of text files.
The main type used with TextMate… ;)
Many editors use a combination of content detection and file extension to figure out the file type. (That's a hint, Allan! :-)
TextMate does that as well via the firstLineMatch in grammars.
Though having to infer file type from content is IMHO often a bad idea.
Consider a hypothetical file browser which allows you to specify user actions based on the file type. If you are browsing a network share, showing the proper actions for your files now require sending (lots of) content over the network.
You may also browse /etc where some files are readable only by root. The file browser probably has a way to request admin privileges when needed, so should it have a demon (running as root) help it determine the file types?
There is also the case of envelope file types, for example if a file has the magic gzip header, should it be decompressed and resubmitted to a file type test?
How can I get off this mailing list. I have unsubscribed two times allready.
Andreas
On 07.01.11 09.29, "Allan Odgaard" mailinglist@textmate.org wrote:
On 5 Jan 2011, at 20:16, Steve King wrote:
[] The 'file' command does this pretty successfully, though it does sometimes get fooled trying to identify the specifics of text files.
The main type used with TextMate ;)
Many editors use a combination of content detection and file extension to figure out the file type. (That's a hint, Allan! :-)
TextMate does that as well via the firstLineMatch in grammars.
Though having to infer file type from content is IMHO often a bad idea.
Consider a hypothetical file browser which allows you to specify user actions based on the file type. If you are browsing a network share, showing the proper actions for your files now require sending (lots of) content over the network.
You may also browse /etc where some files are readable only by root. The file browser probably has a way to request admin privileges when needed, so should it have a demon (running as root) help it determine the file types?
There is also the case of envelope file types, for example if a file has the magic gzip header, should it be decompressed and resubmitted to a file type test?
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Well, I may have been less than precise here.
What I'd like is to remove the .txt extension from the *tabs*. I don't mind them in the side bar or elsewhere. But when you add 4 characters to each file in your tabs bar, you loose a LOT of space!
Thanks for the pointers, btw.
-- Owen
However, I can thing of several cases where the only difference between two tabs might be the suffix (application.js and application.rb, f.e.), so you'd be introducing some hunt-and-peck to the interface.
Walter
On Jan 8, 2011, at 1:02 PM, Owen Densmore wrote:
What I'd like is to remove the .txt extension from the *tabs*. I don't mind them in the side bar or elsewhere. But when you add 4 characters to each file in your tabs bar, you loose a LOT of space!
I use navigate to file every time I switch, much faster than trying to find a darn tab!
Mikael Henriksson
Tel: +46 (0) 730- 393 200 mikael@zoolutions.se
On Sun, Jan 9, 2011 at 3:32 AM, Walter Lee Davis waltd@wdstudio.com wrote:
However, I can thing of several cases where the only difference between two tabs might be the suffix (application.js and application.rb, f.e.), so you'd be introducing some hunt-and-peck to the interface.
Walter
On Jan 8, 2011, at 1:02 PM, Owen Densmore wrote:
What I'd like is to remove the .txt extension from the *tabs*. I don't
mind them in the side bar or elsewhere. But when you add 4 characters to each file in your tabs bar, you loose a LOT of space!
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 2011-01-08 21:32, Walter Lee Davis wrote:
However, I can thing of several cases where the only difference between two tabs might be the suffix (application.js and application.rb, f.e.), so you'd be introducing some hunt-and-peck to the interface.
That problem's already there, if you have a project containing files with the same name but in different directories. Take multiple files named "index.html", for example, or "Makefile". There's no convenient way to tell them apart. I certainly wouldn't want the full pathname displayed on the tab, but it'd be kind of nice to have the current file's path displayed in the title bar.
On Jan 10, 2011, at 1:47 PM, Steve King wrote:
but it'd be kind of nice to have the current file's path displayed in the title bar.
it is, already. ⌘ + click on the file name in the title bar.
Yes I know it's not convenient having the entire location there, but it's a Mac. They are about looking good.
-
AB -
Allan Odgaard -
Brad Rice -
Mark Jackson -
Mikael Henriksson -
Owen Densmore -
Rob McBroom -
Steve King -
Walter Lee Davis -
Watts Martin