Hi all,
I have been using TextMate since December last year and I have found myself using it like more and more as some sort of Finder replacement. At least for text-files that I can open and edit in TextMate. As TextMate is my primary programming environment where I edit source code, ini-files, etc, I have a problem when I open a file for "browsing". I mean when I open a file with no intention to edit it but to read it, copy code sections, check how certain functions are implemented, etc. The problem, or let me say the inconvenience, is that the file remains open as a tab and I have to manually close it.
I could think of two ways to open a file: 1 - For editing, 2 - For browsing. When a file has been opened for editing TextMate would have the same behaviour as today. When a file has been opened for browsing I could think of a behaviour that close the file as soon as I leave it.
For now I have no idea on how to select between open edit vs. open browse but one way could be to use a combination of ctrl, alt or command key to open browse.
Kind Regards /Anders I
On Jan 29, 2005, at 16:05, Anders Isaksson wrote:
I could think of two ways to open a file: 1 - For editing, 2 - For browsing. When a file has been opened for editing TextMate would have the same behaviour as today. When a file has been opened for browsing I could think of a behaviour that close the file as soon as I leave it.
I take it you are new to this list. There has been _a lot_ of discussion in the past about tabs and my current plan is to make it behave similar to Safari. So normally a file is opened in the active tab but holding down a qualifier (or similar) will open it in a new tab (and a new untitled tab can also be opened first, before opening a file etc.).
Yes, I'm quite new to the list, and what you describe sounds rather good. In addition to this I have another idea (that also may have been discussed in the past). As I can do in Safari, it would be good to be able to open a file in a new separate window. Like if you press the command key when you klick a link on a web page you ge a new Safari window.
Sometimes I need to have more the one file open and visible on the same time and this would give me a TextMate window without tabs and the project drawer.
Regards /Anders I
On Jan 30, 2005, at 3:42 AM, Anders Isaksson wrote:
Yes, I'm quite new to the list, and what you describe sounds rather good. In addition to this I have another idea (that also may have been discussed in the past). As I can do in Safari, it would be good to be able to open a file in a new separate window. Like if you press the command key when you klick a link on a web page you ge a new Safari window.
Sometimes I need to have more the one file open and visible on the same time and this would give me a TextMate window without tabs and the project drawer.
I've needed this too. Although what would be really nice is a feature similar to jEdit's window splitting. My apologies if this has already been discussed. I'm rather new to the list as well.
- Justin
On 30. jan 2005, at 15:16, Justin Blake wrote:
I've needed this too. Although what would be really nice is a feature similar to jEdit's window splitting. My apologies if this has already been discussed. I'm rather new to the list as well.
Oh yes it has, but you are forgiven, son ;-). I believe it is on the todo list also.
Maybe there should be a TextMate/Macromates Tada List?
I notice that on many beta lists, feature requests come in over and over again during the life of the list. Archives help and it's nice to have a pulse on the most requested features, but it's also nice to know what's up and coming -- and what's already been requested.
Chris
Sune Foldager wrote:
On 30. jan 2005, at 15:16, Justin Blake wrote:
I've needed this too. Although what would be really nice is a feature similar to jEdit's window splitting. My apologies if this has already been discussed. I'm rather new to the list as well.
Oh yes it has, but you are forgiven, son ;-). I believe it is on the todo list also.
On Jan 31, 2005, at 18:31, Chris Messina wrote:
I notice that on many beta lists, feature requests come in over and over again during the life of the list. Archives help and it's nice to have a pulse on the most requested features, but it's also nice to know what's up and coming -- and what's already been requested.
Yes, I'll most likely create a request tracker in not so long. I know ready-to-use packages exist, but I really do not like any of these, and it's far to much work for me to maintain these (I don't want to go to a web-page to administrate my stuff) and I don't think they generally make a very good job at providing a transparent list of requests (with status) to other users.
So I'm thinking something super simple where the user just fills out a summary and description and I'll do a reject/accept on the item when I feel like it. No need to require users to create accounts etc.
Then we can always let it evolve from there, like allow other users to add comments/votes, I may add an ETA (in form of a version number, but I'll generally like to avoid that) etc. -- and maybe I'll end up with Bugzilla, but let's pray I don't ;)
Overkill in some cases, underkill (?) in others, but Trac (http://www.edgewall.com/trac/) really does fit a nice middle ground. With the integrated Wiki and repository browser it's a three-birds-with-one-stone sort of thing.
The Roadmap feature would do a respectable job of solving the problem discussed in Chris' original post.
On Jan 31, 2005, at 12:44 PM, Allan Odgaard wrote:
Yes, I'll most likely create a request tracker in not so long. I know ready-to-use packages exist, but I really do not like any of these, and it's far to much work for me to maintain these (I don't want to go to a web-page to administrate my stuff) and I don't think they generally make a very good job at providing a transparent list of requests (with status) to other users.
On Jan 31, 2005, at 12:58 PM, Jack Baty wrote:
Overkill in some cases, underkill (?) in others, but Trac (http://www.edgewall.com/trac/) really does fit a nice middle ground. With the integrated Wiki and repository browser it's a three-birds-with-one-stone sort of thing.
The Roadmap feature would do a respectable job of solving the problem discussed in Chris' original post.
On Jan 31, 2005, at 12:44 PM, Allan Odgaard wrote:
Yes, I'll most likely create a request tracker in not so long. I know ready-to-use packages exist, but I really do not like any of these, and it's far to much work for me to maintain these (I don't want to go to a web-page to administrate my stuff) and I don't think they generally make a very good job at providing a transparent list of requests (with status) to other users.
Did I just top-post that last message? Darn that Mail.app! Sorry.
-
Allan Odgaard -
Anders Isaksson -
Chris Messina -
Jack Baty -
Justin Blake -
Sune Foldager