This addition to the Xcode bundle adds Xcode debug support to the bundle.
This does _not_ rebuild the debug configuration before invoking debugging,
however that can be added trivially to this.
When writing bundles, the current environment contains the variables
TM_INPUT_START_(LINE|LINE_INDEX) to contain the corresponding data
from the beginning of the selection. If I need to have a look at the
text at the beginning and end of the selection I would use these
variables for the start and TM_LINE_(NUMBER|INDEX) for the end.
Fine - as long as I just select downwards (placing the selection
start-point to the left and/or higher than the selection end-point.
If I do an upward selection this will leave me with no information
about the (lower) end-point at all as the current position equals the
Is it possible to have some additional TM_INPUT_END_(LINE|INDEX)
variables to definitely catch the end-point data no matter what kind
of selection (downward/upward) has been used?
It would also be convenient having both the start-/end-point line
content (not only the current) as an environment setting which saves
reading the whole document for one of two lines again.
thanks so far
Dear Haris (or whomever else!),
The latest SVN versions of the latex bundles don't seem to respect the
value of TEXINPUTS. Instead, the bundle has the lines
# Add our tex directory to the TEXINPUTS variable so e.g. pdfsync is
found (even when the user hasn’t installed it)
# preceeding colon stands for default search paths. Search them first so
if user installed pdfsync it'll use that one
The problem is that this doesn't actually *add* to the TEXINPUTS; it
It should probably be something like
but with some better shell-substitution to take care of possible
previous values or lack thereof for TEXINPUTS.
I've tried the TM CodeBrowser plugin (a very good idea btw) and I
well (prototype.js for example). I searched the list archives and
found a broken link to CodeBrowser2...anybody have any advice?
The Textmate help section on printing states:
"There are plans to improve the printing capabilities, but until
then, there is also a command in the Source bundle (View Source as
PDF) which produces a PDF from the current source using enscript and
has syntax highlighting enabled for supported languages."
I have v 1.5.4 (1324) of Textmate and don't see this option in my
Is it still available somewhere.
I'd like to be able to print and get the syntax coloring in the printout.
Thanks for any pointers.
- Stephen Bannasch
Concord Consortium, http://www.concord.org