Has anyone created an upload command when mp3s are dragged onto a
document? This would be a great podcasting feature for the blogging
bundle.
Thanks,
Graham English
I have noticed that if I set Line Endings to "CRLF (Windows)" (when
collaborating with windows people), line endings are correctly
translated to windows style. I forgot to set Textmate back to Unix
standard (LF), opened a text file, and when I next saved it it had
CLRF line endings. When I changed Textmate back to LF mode, the line
endings stayed as CRLF. Even if I delete then re-do all the
linebreaks, they are still CLRF. I need to get this sorted right
away, so I have used Fink to install dosunix to convert these
"CRLFed" documents.
Is this a bug in TextMate? It would be nice if there was some way to
set the line endings by file, rather than having an app wide setting.
Also, it would be great if this could be put in a bundle (LF->CRLF
and vice-versa).
Thanks,
Nick Forge
Hi All,
I am trying to use FileMerge for the 'Diff with...' commands in the
Subversion bundle.
The help file says to set $TM_SVN_DIFF_CMD to fmdiff. I guess that
should be fmdiff.sh, which needs to be downloaded and installed first
from elsewhere (help should mention that).
Anyhow after I did set that up and run a diff, it does open in
FileMerge, but the "Accessing Subversion Repository" panel in
TextMate sticks around until FileMerge is quit. Am I doing something
wrong, or is that a problem with the bundle?
Thanks
Gerd
Hello,
while testing mercurial I noticed that the diff commands in the
Mercurial Bundle behave differently than what I'm used to from the svn
bundle.
When I select a folder in the drawer and issue any diff command using
the subversion bundle, I get a diff for all files under that selected
folder.
The mercurial diff commands always use the currently active file in the
diff commands.
Changing the hg_diff.rb file enables me to select a folder and get a
diff for everything under it:
@@ -6,7 +6,7 @@
module Mercurial
def Mercurial.diff_active_file( revision, command )
hg = ENV['TM_HG'] || 'hg'
- target_path = ENV['TM_FILEPATH']
+ target_path = ENV['TM_SELECTED_FILE'] || ENV['TM_FILEPATH']
work_path = ENV['WorkPath']
path = target_path.sub(/^#{work_path}\//, '')
output_path = File.basename(target_path) + ".diff"
(patch is attached)
While I'm here .. I had to change all diff commands do something like
(
"${TM_RUBY:=ruby}" -I "$TM_BUNDLE_SUPPORT/" <<END
require 'hg_diff'
Mercurial::diff_active_file("-r$rev2 -r$rev1", "Diff Revisions…")
END
) | iconv -t UTF-8 -c
since without the iconv call I'd get empty diff windows (probably
because of incorrectly encoded german special chars inside the generated
diff) -- but I'm not shure if this is just a local problem.
Bye,
Eike
Index: /Library/Application Support/TextMate/Bundles/Mercurial.tmbundle/Support/hg_diff.rb
===================================================================
--- /Library/Application Support/TextMate/Bundles/Mercurial.tmbundle/Support/hg_diff.rb (revision 7253)
+++ /Library/Application Support/TextMate/Bundles/Mercurial.tmbundle/Support/hg_diff.rb (working copy)
@@ -6,7 +6,7 @@
module Mercurial
def Mercurial.diff_active_file( revision, command )
hg = ENV['TM_HG'] || 'hg'
- target_path = ENV['TM_FILEPATH']
+ target_path = ENV['TM_SELECTED_FILE'] || ENV['TM_FILEPATH']
work_path = ENV['WorkPath']
path = target_path.sub(/^#{work_path}\//, '')
output_path = File.basename(target_path) + ".diff"
I'd love to have a command that can put the current symbol on the
clipboard, and this would be short-work if the current symbol where
available via a TM_* variable, but I'm not seeing it.
My particular use case is Python and I'd like to be able to easily
construct "<module>.<class>.<method>" or "<class>.<method>".
I see no way of getting this information, short of writing a python-
specific parser to grab it (using TM_LINE_NUMBER to figure out where
the cursor is). Am I missing something?
j.
I have a user of my FlickrMate bundle getting the following error...
error 63 (File name too long) opening sem /tm_dialog async/
> nilsborchers/4.
> tm_dialog (async_update): Window '4' doesn't exist
> /Applications/TextMate.app/Contents/SharedSupport/Support/lib/
> dialog.rb:83:in /bin/bash: -c: line 1: unexpected EOF while looking
> for matching `''
> /bin/bash: -c: line 4: syntax error: unexpected end of filecall'
> from /Applications/TextMate.app/Contents/SharedSupport/
Support/lib/
> progress.rb:36:in /bin/bash: -c: line 1: unexpected EOF while
> looking for matching `''
> /bin/bash: -c: line 3: syntax error: unexpected end of filecall'
> from /Applications/TextMate.app/Contents/SharedSupport/
Support/lib/
> progress.rb:49:in /bin/bash: -c: line 1: unexpected EOF while
> looking for matching `''
> /bin/bash: -c: line 3: syntax error: unexpected end of filefork'
> from /Applications/TextMate.app/Contents/SharedSupport/
Support/lib/
> progress.rb:47:in /bin/bash: -c: line 1: unexpected EOF while
> looking for matching `''
> /bin/bash: -c: line 3: syntax error: unexpected end of filedialog'
> from /Applications/TextMate.app/Contents/SharedSupport/
Support/lib/
> progress.rb:40:in
It's occurring during the "Browse Flickr Photos" command. If anyone
is familiar with that particular error, could you please let me know
what it might be related to?
Thanks,
Brett
Hi. This may be an another obvious thing I have missed, but:
Running Ruby produces beautiful output, through Rubymate. But running
shell commands splats the output into a plain window, with output and
errors thrown in together, and line endings ignored.
Is there any way to pipe shell output through Rubymate, or any similar
functionality for the shell?
---
Bruno
Hi TextMaters,
I recently started to translate TextMate manual into Japanese.
Subversion repository is located at http://macromates.com/svn/Bundles/
trunk/Manual/pages .
`en` directory is a Markdown version of Allan's original manual,
which I use as a source of translation and as a template. We can,
therefore, expect the same look of the translation, sharing the same
graphics and layout if Allan can tweak his script a bit.
`ja` is used for the translation. Except for a `_read_me.mdown` file,
the directory will have the same file names. My plan is to translate
the all contents quickly but roughly, and polish the translation
later on. At the moment, there's no way to *compile* a book from the
files. (Note: I haven't even translated 5% of the Manual yet.)
**Caution**
TextMate doesn't support CJK at this moment. Users including those
who use [Fake CJK Support](http://macromates.com/blog/archives/
2006/11/09/faking-cjk-support/) are encouraged *not* to open files
other than `_read_me` file in the directory with TextMate. TextMate
or the entire system may hang. You may be able to open, but
converting the Markdown to HTML may also be a cause of this hang.
From my personal experience, handling lots of CJK text prones to
this issue.
Since I can't find anyone else who is using TextMate with a large set
of Japanese text, the problem may be personal. But for now, my
suggestion is that you not use TextMate to open the files. I get a
few emails saying I'm putting virus, but .mdown files are just plain
text files.
Takaaki
--
Takaaki Kato
http://samuraicoder.net
