I'm not quite sure if this is a bug per-se, but I ran into a problem
attempting to create C & CPP template files, related to how the existing
Objective-C template shell works (and interacting with it):
When you create a new file from template using File->New From Template->foo
the environment variables for $TM_NEW_FILE and $TM_NEW_FILE_DIRECTORY seem
to get interpreted such that they wind up pointing at a directory under that
user's /tmp. The problem is that if any template shell script has already
created an "untitled<n>.h" file there, that file causes the new template
shell script's "exist" test to fail, and you wind up loading the (colliding)
file generated by the prior template shell script. When dealing with three
different template types (C, C++, and Objective-C) all who expect to also
generate a .h file, the chance of such a collision becomes very high.
I looked at possibly using a timestamp to try and differentiate, but that
causes a problem if the user actually triggers the template shell script
from the Project window. In that case, the script receives
properly-populated $TM_NEW_FILE and $TM_NEW_FILE_DIRECTORY variables, and
thus you don't have the same problem of trying to avoid "tmp" naming
collisions.
It seems like there are a couple of obvious solutions:
1. TextMate could populate a variable to indicate whether the template is
being run from the Project window (in which case $TM_NEW_FILE and kin are
properly populated, and should be unique), or from the "File->New From
Template" menu item (in which case they are not, and you need to avoid
collisions because all template scripts are dumping in the same tmp
directory, using "untitled"-based names).
2. Alternately, in the "File->New From Template" case, TextMate itself
could initially provide a _unique_ $TM_NEW_FILE_BASENAME and friends
(perhaps append a `date "+%y%m%d%H%M%S"` to the basename?). That would
prevent collisions in the tmp directory even when multiple templates
provided files with overlapping file extensions.
There also appears to be an issue over time of these left-over template
shell script file "breadcrumbs" created when "untitled<n>.foo" files are
initially created, but the user presumably saves the file with a real name
afterwards. There really doesn't appear to be any way for template scripts
to clean up the tmp dir after themselves. Not a big deal if the filename
collision problem gets solved, but eventually they'll start to create a fair
amount of "Spotlight clutter", etc. which can become an issue.
Love the program, and am quite impressed by how much is already possible
with V1's facilities. That said, I'm really looking forward to V2 and the
more powerful snippets/templates/etc. I've been rather spoiled by Slickedit
on PC, and keep hoping TextMate will offer similar abilities (I refuse to
use that X-Window abortion Slickedit calls a "Mac version").
Thanks!
-John W.
--
View this message in context: http://old.nabble.com/%22File-%3ENew-From-Template%22-shell-script-%22issue…
Sent from the textmate users mailing list archive at Nabble.com.
I doubt this can be done with the current version of TextMate but I want to
put it out there and see what people suggest.
When working on git repositories, I find myself jumping from branch to
branch often. We use branches heavily in my company for everything from
little on-demand bug fixes to entirely new features. Most times switching
branches means closing all tabs and opening tabs relevant to the selected
branch. It also often involves expanding a number of folders in the drawer
but this happens less often as I am a keyboard freak and rarely use the
drawer.
It would be awesome if switching branches could trigger TM to close the
current tabs and open the ones being worked on the last time this branch was
selected. Even better if cursors were moved to the right positions too.
Now, I realize this is too specific for TM to have natively but it would be
nice nonetheless. I wonder if a plugin could do this? Maybe by using git
branch identifiers as keys to layout specifications that can be saved
elsewhere as plugin data.
Does this sound doable? Can anyone point me in the right direction to
documentation that I can use to maybe give this a shot? I'm happy to work on
a plugin if people are interested in something like this.
Cheers.
Luis
Hi all,
Is there any way to change the highlight color of the text you are
searching for? I know that there is a Selection color option in the
Preferences, but I would rather leave that at the standard pale blue
(in the Mac Classic) for normal selection highlighting. I would like
to have the found text show with a background color of red, or some
shade of red. I find it difficult sometimes to scan a lot of real
estate in the edit window trying to find the text that was found. A
more dominant color would fit the bill here nicely.
Thanks,
Barry
Hi
I would like to make a command or a macro
to preview a file latex2e.html. This the LaTeX2e reference manual
http://www.tex.ac.uk/tex-archive/info/latex2e-help-texinfo/
1 ) I don't know how to make this
I try to convert latex2e.html to latex2e.markdown
with textmate and I try a command like
. "$TM_SUPPORT_PATH/lib/webpreview.sh"
html_header "LaTeX2e Help" "LaTeX"
"$TM_SUPPORT_PATH/lib/markdown_to_help.rb" "/Users/ego/Library/latex2e.markdown"
html_footer
but there is a problem. Some links don't work
and sometimes I need to stop the task (wheel :) )
I try with latex2e.html it's better but I get
some similar problem.
2 ) If I open latex2e.html and I use show web preview then
it's fine but I don't know how to get this with a command
3 ) is it possible to record a macro for something like that ?
4) I can make something like that
. "$TM_SUPPORT_PATH/lib/webpreview.sh"
html_header "$title" "Latex2e Reference manual"
open -a safari /Users/ego/Library/latex2e.html
html_footer
But I would like to make this with web_preview and perhaps without
a simple css.
Thanks Best regards
Alain Matthes
Hi
I've been digging in the sequence of calling that makes ^H to fail in C++ (TM 1.5.9 1589). It seems that
/Applications/TextMate.app/Contents/SharedSupport/Support/bin/html_man.sh
looks for
RMAN_1='/Library/Application Support/Apple/Developer Tools/Plug-ins/DocViewerPlugIn.xcplugin/Contents/Resources/rman'
RMAN_2='/Developer/Library/Xcode/Plug-ins/DocViewerPlugIn.xcplugin/Contents/Resources/rman'
and vuala! the second one does not exists and the first one returns nothing looking for simple words like "printf"…
I am not aware of previous threads related with this one, but I don't doubt at all that there must be many.
Is there any workaround, update, or change I should do to have help working?
- juan falgueras
>
> Date: Tue, 12 Jan 2010 09:05:55 +0100
> From: Allan Odgaard <mailinglist(a)textmate.org>
> Subject: [TxMt] Re: LaTeX bundle; reference/citation completion bug +
> suggested fix
>
> On 11 Jan 2010, at 09:55, Andrew Hill wrote:
> > it seems to be the character %0A
>
> 0x0A is not shown as a diamond with show invisibles.
>
> Try instead to select the diamond in TextMate and press ??X to
> convert it to hexadecimal.
>
>
Right you are!
My apologies and thanks for teaching me a new trick. I also just discovered
if I open up the "Edit -> Special Characters..." menu item, I can drag and
drop the character into the window there to see what it is.
Anyway, it's the 0x0D character (carriage return) — I suspect my browser or
the clip-board decided to clean up the line endings of the copied/pasted
text by converting CR to LF before...
So it's picking up the CR char because my .tex file has CRLF line endings,
and I guess the ruby script is finding ends of lines by LF character only.
To test this, I converted the document to LF line endings and the original
ruby script worked fine (as did the one with the .strip addition).
With the CRLF line endings, the .strip (or better yet a removal of just
trailing CR) is required. Alternatively, can ruby deal with CRLF line
endings on its own?
For completeness I tried saving my document with CR line endings, and the
error message was basically a re-paste of my entire document as the filename
(i.e. Ruby is not parsing the CR chars as line endings, only LFs). Though I
doubt anyone really uses CR line endings...
Andrew
Hello Hans,
thanks for the hints, but I believe you misunderstood me. I don't want to change syntax highlighting within the editor, but the colors in the output, which are now blue on blue. I have found out that there's a stylesheet for that somewhere on my system but I can't seem to find it. At least, it is not included in the bundle itself.
Regards,
Paul
