Hi,
In the Fortran bundle, there doesn't appear to be any support for
comment lines beginning with an asterisk, only for comments beginning
with C or c. I have tried to add this in to the language but I am
quite unfamiliar with how to do this properly and am I not very
familiar with regular expressions. I tried adding the following in
the bundle editor (using comment.line.c.fortran as an example) but it
still does not recognize lines beginning in * as comments. Any help
would be appreciated.
{ name = 'comment.line.asterisk.fortran';
begin = '^[*]';
end = '$\n?';
beginCaptures = { 0 = { name =
'punctuation.definition.comment.fortran'; }; };
patterns = ( { match = '\\\s*\n'; } );
},
Thanks,
Stefan
Hi folks,
I have been experimenting Scala lang a bit, and it auto open the source in
PlainText mode with TM, which is fine for me at the moment. But the source
keep having RedDot underlines on many words that made it very hard to read!
How can I disable this?
Thanks,
Zemian
Especially when coding python, I would like TextMate to auto detect if
the current file is using space over tabs.
When using libs from different projects, it's tiresome to remember to
check and switch everytime you jump between files (editing in
different repos)
Instead of detecting this, I would relly like TM to remember my
selection,
Now, if I switch to Soft Tabs, jump back to my Tabbed file I need to
change every time (global setting)
any magic tricks!?
best
/d
I've been trying to use the TODO bundle with a very large project
containing a bunch of external/imported code which I don't control. In
this project, Show TODO Items... takes a veritable eternity to run
because of the volume of code it must scan. My project, however, is
set to filter out a significant amount of this within TextMate, but
these filters are being ignored by the bundle.
Upon investigation, it seems the issue is the core textmate.rb support
library whose ProjectFileFilter (used by each_text_file) reads the
TextMate prefs for its file/dir filters, rather than getting them from
the current project first. Indeed, there doesn't seem to be any
reference to the current project filters in the TM_* environment
variables or in textmate.rb.
It would be great to see this filters respected by some of these core
library commands where it seems they really should be taking effect.
So, I have noticed that when I have multiple files open each with the
same name (but in different directories) and I compile one and then
another, TextMate doesn't seem to be telling Skim that they are
actually different files. I never had this problem before. I posted
before about how one time I upgraded and I noticed that my compiled
PDF no longer came to focus upon compiling, and at the same upgrade
this problem started. I start compile one file and it opens the PDF,
but when I try to compile another file with the same name it doesn't
open the new PDF because it just thinks that it's the same PDF I
already have open. Are these two symptoms connected? Has anyone
found out why the change in functionality? And/or how to revert it?
I almost wish I could downgrade, but I tried the SVN thing that
someone said to try and it didn't work for me.
Keith
Hi guys,
I downloaded the jQuery bundle from the repository, however, I'm not happy
with a few things, and need to make local corrections.
One of those things is the default scope it gives it (source.js.jquery).
Since jQuery is available in every JS file I am editing, is there a way to
mass edit the entire bundles scope to be source.js ?
Every time I've manually gone through the bundle and edited the scope, every
time I restart, it's back to being source.js.jquery.
Is there a way to mass edit the bundle scope, AND have it stick?
Thanks guys,
--
View this message in context: http://www.nabble.com/Mass-editing-the-bundle-scope-tp14695883p14695883.html
Sent from the textmate users mailing list archive at Nabble.com.
I have a problem with LaTeX Watch. If I save a file with changes, it
endlessly reloads the .pdf until I quit Skim.
I set TM_LATEX_WATCH_DEBUG=1 but saw no messages in the console.
I agree; it would be best to always end up at the end
of the panel, so you can rerun if needed after making changes.
Thx for the great Latex Bundle and the Latex Watch, etc.,
M.P.
>
> Message: 4
> Date: Sun, 6 Jan 2008 17:43:52 +0000 (UTC)
> From: Chris <listservs(a)mac.com>
> Subject: [TxMt] Typeset and View issue
> To: textmate(a)lists.macromates.com
> Message-ID: <loom.20080106T174059-278(a)post.gmane.org>
> Content-Type: text/plain; charset=us-ascii
>
> When compiling LaTeX documents, the Typeset and
> View pane works properly when invoked from by running
> the compile command from the contextual menu, or by
> using the hotkey combination. However, when commands
> are run by clicking the buttons provided at the bottom
> of the T&V panel at the end of a completed command
> (e.g. re-run latex, run bibtex), the panel does not
> scroll down automagically to follow the most recent
> output. This makes it hard to follow.