Talk:TextMate

message: My informationt that there's no easy way to modify TM's shourcuts and behaviour of built-in functions has been removed. I disagree - I've asked about things like indentation using Tab key or prefilling search with selected text on Cmd+F - the answer was that these things can't be done and I should stick to built-in shortcuts.  --unsigned comment by user:84.92.248.233
:done, thx —remark left by user:84.92.248.233 upon removing this comment
I'm adding the comment above back in as wikipedia values keeping discussions around.  This text was added to the "limitations" section to address the concern noted above:
:"Because TextMate is not tightly coupled to a scripting language, as Emacs is to elisp, it is impossible for users to have complete control over the behavior of some built-in commands such as those which indent sections of text or those which move columns around; however, almost every useful action can be accomplished with TextMate's macros and commands."
—jacobolus (t) 21:33, 25 August 2006 (UTC)
thread_title:  Modifying shortcuts 

message: A note was added by an anonymous user that (s)he could get right-to-left languages working in TextMate.  As the TextMate developer has said that this doesn't work, I took the claim out, but I would like to hear more if in fact that is the case.  --jacobolus (t) 23:31, 23 September 2006 (UTC)
thread_title:  Right-to-left support 

message: Does TextMate support dragging text? I know e (the Windows port of TextMate) does not, but e doesn't support code folding, either. — Brianary 16:59, 19 March 2007 (UTC)
replies: text: Yes, like almost all Mac applications, TextMate supports the dragging of text. --jacobolus (t) 10:39, 26 March 2007 (UTC)
thread_title:  Dragging Text 

message: > the point of adding a GUI is not to match "look and feel".
I have not claimed that at all. The sentence, as it is now, does not assert that all a text editor needs to make it "simple and ellegant" is a GUI, but that it is the case with a macintosh GUI only. It also doesnt state that the editor is "simple and elegant", but that its just the Macintosh GUI that makes it that way.
> The point is that the GUI *is* simpler for users to navigate than a purely textual interface.
As I said, I have not disputed that.
> "Elegance" is a bit harder to quantify, as it is very subjective, but again,
So it should not be mentioned in a general description of a text editor.
> if you like, I can give you dozens of quotes about the elegance of the Macintosh, especially as compared to textual interfaces.
And I can on the other side give you dozens of dozens of articles statin the contrary. This issue _IS_ a matter of the point of view, so it should be described more neutrally. --Rhun 12:16, 22 April 2007 (UTC)
replies: text: Then write a better sentence.  Just swapping out a couple of words is a cop out, and doesn't cut it.  --jacobolus (t) 12:20, 22 April 2007 (UTC)
replies: text:  I also don't have the time to exchange the wording until you nod it through graciously. You either can write that any GUI makes a text editor "simple and elegant" (which we both know isn't the case, and vim and emacs both are GUI editors nowadays) or leave it away, like you have done now. Just building on a specific gui library doesnt make a program "simple and elegant" (which then would also logically apply to the mac ports of vim and emacs, and any other Mac editor under the sun). --Rhun 12:35, 22 April 2007 (UTC)
replies: text:  No, you completely miss the point of TextMate.  Perhaps you haven't used it?  Anyway, the idea is to bring both the customization and power that come from allowing users to program their editors, as well as the discoverability and interface simplicity of a GUI.  This is a very different thing from putting vim inside Gvim, or whatever.  It's not even comparable.  But you're right.  This really takes 3-4 sentences to truly explain why TextMate is more elegant than any other editor.  I'll perhaps put in a better explanation sometime.  I'm sorry that you aren't willing to put any thought into the sentence yourself.  I think the introduction is much poorer for that sentence's removal.  So it goes.  --jacobolus (t) 12:40, 22 April 2007 (UTC)
thread_title:  Simplicity and elegance 

message: Regarding my edit changing "its basic feature set has a steeper learning curve than simpler graphical editors" to "its basic feature set may require more learning...", which was subsequently undone by Jacobolus:
The reason "a steeper learning curve" is ambiguous is that it can be interpreted to mean two completely opposite things. Strictly speaking, a steep learning curve implies fast learning (the curve plots proficiency over time) and so is a good thing. But many (probably most) people think it means that something is hard to learn. Given this ambiguity, I think it's best to avoid the term altogether. Forlornturtle 10:46, 4 June 2007 (UTC)
replies: text: Ah.  That makes sense then.  I've only ever heard "steep learning curve" or "shallow learning curve" used to mean, respectively, hard to learn or easy to learn.  Go ahead and make such a fix.  The sentence could maybe even be rewritten to be a bit more specific; it's a bit hard to characterize such things in a way which is both informative and NPOV, as the difficulty to learn something is inherently subjective.  Anyway, go ahead and put back that change if you want.  --jacobolus (t) 08:21, 5 June 2007 (UTC)
thread_title:  "Steep" learning curve 

message: What do folks think about adding a link to this interview in the external links section:
http://blog.johnjosephbachir.org/2007/10/01/interview-with-allan-odgaard-creator-of-textmate/
The interview was performed by me. --Johnjosephbachir (talk) 21:33, 15 December 2007 (UTC)
replies: text: Sounds great. :) --jacobolus (t) 23:09, 15 December 2007 (UTC)
thread_title:  Linking to interview on my blog 

message: Hi.  Courtesy warning...  I intend to remove the "Limitations" section of the article.  I'll explain my rationale for why it doesn't belong in an encyclopedia.
# The actual list of limitations of TextMate is infinite.  No, really, it is.  When do you stop listing things a product *cannot* do?
# If we did agree that a space-limited list of limitations is appropriate for an encyclopedia, then we'd have to decide what arbitrary subset of limitations we were going to include.  What's the criteria?  A mention of the limitation in popular press?  In a reliable source's review of the product?  From the product's own literature?  (user forums are not acceptable and citing a primary source like TextMate's literature is not a good practice in general)
# Since this is evolving software, there is a high likelihood that we publish a limitation but that limitation gets removed soon after or just muddled in details like "limitation of versions 1.5.04 through 1.5.09 but removed in Preview or Alpha release"
# Comparison articles already exist that, I think, put TextMate's limitations in a useful context.  e.g.  Comparison_of_text_editors#Mac-only_text_editors 
# A limitations section is effectively a section of criticisms, and this is strongly discouraged on Wikipedia.
# The section is a magnet for biased and POV edits.  It's easy to hate and bias an article when the pool of materian (limitations) is unlimited.
Thanks for listening.  If anyone feels strongly that some limitations of TextMate need to be in the article, then those notable limitations can be put into the regular part of the article along with a reliable source. --Ds13 (talk) 17:02, 17 August 2012 (UTC)
replies: text: I have no particular pro or con opinion; I think that it should be consistent either way. Either there are limitations mentioned by every editor, or it should be by none, simply because otherwise bias kicks in and things become less objective as a whole, since you may have 2 out of 10 editors with "limitations" but the other 8 none. What could perhaps be a compromise would be an OBJECTIVE table of features. This is also difficult but doable. 2A02:8388:1640:9D80:3AD5:47FF:FE18:CC7F (talk) 06:17, 24 August 2017 (UTC)
thread_title:  Removing the "Limitations" section 

message: Hello fellow Wikipedians,
I have just modified 3 external links on TextMate. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20060820174030/http://maczealots.com/reviews/textmate/ to http://maczealots.com/reviews/textmate/
*Added archive https://web.archive.org/web/20060514032521/http://www.drunkenblog.com/drunkenblog-archives/000347.html to http://www.drunkenblog.com/drunkenblog-archives/000347.html
*Added archive https://archive.is/20041204223039/http://www.xmldatabases.org/WK/blog/2129_A_cool_new_text_editor_-_TextMate_-_Mac_OS_X.item to http://www.xmldatabases.org/WK/blog/2129_A_cool_new_text_editor_-_TextMate_-_Mac_OS_X.item
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 03:29, 17 January 2018 (UTC)
thread_title:  External links modified 

message: A permissive software license allows more things to be done with the software by the user. A permissive license that also compels future developers to be similarly permissive is more permissive, not less. A license that allows future developers to be less permissive - in other words allowing them to falsely claim certain exclusive rights over public property - is a less permissive license.
Analogy: A person who takes all the books from a public library and offers them for sale is a thief, not a hero liberating books from the tyranny of the library system. TooManyFingers (talk) 00:17, 2 April 2024 (UTC)
replies: text: Please don't bring weird ideological GNU advocacy to unrelated contexts. This notion of 'permissive' meaning 'makes fewer copyright restrictions' is in common currency and is not confusing. See e.g. Permissive software license. Cf. WP:NOTADVOCACY. –jacobolus (t) 01:32, 2 April 2024 (UTC)
thread_title:  "... more permissive license"