Has anyone out there come up with a way to insert "end-of-line"
comments. As a former vim user, I had a plugin that would insert a
comment on column 55 of the given line. I would love to be able to do
the same in textmate. Any suggestions?
---
chad gulley
cag(a)adfitech.com
www.adfitech.com
405-715-8083
Hi
Markdown does not do well codeblocks in between list items
<http://daringfireball.net/projects/markdown/syntax> :
To put a code block within a list item, the code block needs to be
indentedtwice — 8 spaces or two tabs:
* A list item with a code block:
<code goes here>
- Juan Falgueras
So maybe my last email (pasted below) was poorly worded. I'll try again...
I've found 3 highlighting bugs and 2 export bugs in the Markdown
bundle. I'd fix them myself but the Markdown Bundle's kung-fu is too
much for me to handle.
Highlighting Bugs
-----------------
1. Raw code nested inside blockquotes require indentation by
two tabs, not one.
2. Same rule applies to lists.
3. Reference-style links should allow titles to be listed on
the next line, indented with as many tabs as you'd like.
All three of these are *just* highlighting bugs, they export to HTML just fine.
Export to HTML bugs
-------------------
1. Raw code nested inside blockquotes is incorrectly exported
with two leading spaces inside the pre/code tags.
2. According to Markdown syntax, reference-style link's titles
are allowed to be inside single-quotes.
And that's it. If you need an example to paste into TextMate see here:
<http://pastie.textmate.org/private/tetzlcuww7rmb8jkcff4ia>
--oliver
------------------------------------------------------------
On Fri Dec 5 at 20:55:31 Oliver Taylor wrote:
> I was playing with Markdown (yeah I'm that kind of nerd) and I ran
> into the following bugs:
>
> This message is also on pastie in case the list strips tabs:
> http://pastie.textmate.org/private/tetzlcuww7rmb8jkcff4ia
>
> - - -
>
> > This text is indented from the bracket ">" by one tab
> > (which is allowed in Markdown) and is mis-highlighted
> > by TextMate as a nested code block.
> > If, however, I indent by 4 spaces TextMate highlights
> > this correctly.
>
> > When blockquote-nested code blocks, like this paragraph, are
> processed into HTML they include two spaces at the beginning of the
> code block.
>
> * Code blocks in lists must also be indented by 2 tabs.
>
> This should be highlighted as code.
>
> Processing this to HTML works as expected, and does not
> include the blockquote's "2 space" bug.
>
> - - -
>
> [Links](http://example.com) can be [written][foo] a number of
> [different ways][bar].
>
> [foo]: http://example.com
> "This line begins with 2 tabs. It is highlighted as code, but
> processes as a title (as it should)"
>
> [bar]: http://example.com 'single quoted titles don't highlight or
> process, but should be allowed according to the Markdown syntax'
>
> Is there a specific reason single-quote titles aren't allowed?
>
> - - -
>
> Also, shouldn't links like this <http://example.com> be scoped as
> `string.other.link.markdown` or something so that they highlight like
> every other kind of link?
>
> - - -
>
> Thanks for indulging me.
>
> --oliver
Hi there,
Due to some trouble with my current laptop, I had to borrow another
one and as a consequence, did a fresh TextMate install on a fresh user
account on OS X 10.4.11. Next step was getting GetBundles, which
failed with
/bin/bash: line 15:
/Users/someone/Library/Logs/TextMateGetBundles.log: No such file or
directory
I had to create a ~/Library/Logs to avoid the problem. I guess this
qualifies as an easily corrected bug.
Édouard
Hi all,
Is it possible to fix the YAML inline-hash syntax highlighting?
Working with Symfony, it's very common to have inline hashes in the
routing.yml file. They look something like:
feed_enhanced:
url: /recently-added.xml
param: { module: feed, action: enhanced }
The YAML bundle considers "feed, action: enhanced" to be a value for
"module:" where "action:" should be a new key.
Is there a fix? I've briefly looked at fixing it, but I'm not
familiar enough with the TM syntax definition to figure this out on my
own.
Thanks,
--
-Jacob
Hey everyone,
I'm trying to piece something together and I figured I'd ask if it was
possible before I put all of the mental effort into it.
I use the "find email address in address book" bundle almost daily. I
was wondering if it is possible to configure similar functionality for
the calendar? I want type in a word from an event's name and the
command would pull the full name, location, start and end date from
iCal. Is this possible?
I'm not a programmer but I was hoping to modify the existing bundle.
I *think* the CalCalendarItem and CalEvent frameworks provide the
necessary information to pull this off but I wanted to make sure that
it was feasable before I attempted something so far above my pay grade.
j.
I am trying to create a command that takes input as "selection or
scope", so I set the input option accordingly.
I set the scope selector to string.quoted.double.block.python
However, when I press the key equivalent, my command receives the
entire file as input instead of just the string.
Can you already see something that I am doing wrong? Screenshots attached.
Thanks,
Abhi
There must be a key command for this, but I can't find it. In php
mode, if you have an area selected, how do you wrap it with /
* ..selection.. */ ?
Thanks.
smosk wrote:
>
> Just switched over to textmate from the pc port e text editor.
>
> I see how to column select, but I can't figure out how to select multiple
> words (or sections of text).
> In e, you just hold control and select arbitrary sections of the document.
>
> Please tell me you can do this! I thought this was one of the big draws
> to textmate. It certainly was for me when I switched to e.
>
Uhm I'm not sure I understood anyway
ctrl + (right|left) arrow and you select many words.
Otherwise command + mouse and you select whatever rectangular shape you
want.
Look in "Edit -> select"
--
View this message in context: http://www.nabble.com/Multiple-Selections-tp20930086p20940328.html
Sent from the textmate users mailing list archive at Nabble.com.
Hi,
There were a number of QuickTime tutorialsI watched a month or so ago
showing how to use TextMate (general editing info: autocompletion, tag
balancing, keyboard equivalents, etc.) that were of interest to me as
a long-time BBEdit user who's begun the switch to TextMate.
I can't remember how I got to them, but I thought it was via
macromates.com, but I can't find them any more. Googling "textmate
videos" brings up lots of stuff, but not the ones I'm looking for.
The person doing the walkthroughs had a northern European accent; he
was very soft-spoken (but had very good English). Does this sound
familiar to anyone?
--
Regards,
Christopher Mackay
I'm facing compiling problems after the TM update to 1.5.8 (bleeding
edge).
I save my tex-files in my project in Latin1. As soon as i open a new
file in the project and want to compile it, i get the following error
message.
"LaTeX Error: Command \textcurrency unavailable in encoding T1"
When i save the file with "save as" and make sure TM saves it in
latin1, and i close the file, then the compile process suceeds. I'm
sure I haven't faced this problem with 1.5.7. When i downgrade to this
version, everything works fine. as soon as i upgrade, i have this
problem.
I think TM wants to save everything in utf8. At least i realised that
former latin1 docs were saved as utf8. In the prefs pane > advanced>
saving there is "latin1" listed under "file encoding".
Hope somebody can help me
Is there anything further on this issue? I'm experiencing the same results
for a fresh checkout from an svn+ssh repo, performed through TM.
> On 24 Jan 2008, at 21:59, dave.myron wrote:
>
> >> [...] the default values for the above should become:
> >>
> >> svn log --xml --limit 15 -vr HEAD:1 \
> >> «file» 2>&1 | ruby -- "${TM_BUNDLE_SUPPORT}/format_log_xml.rb"
> >>
> > Digging up an old thread here, but I'm getting these same problems
> > with the
> > latest TextMate and the latest Subversion bundle.
> >
> > When I run the second command above (the *parsed* one with defaults)
> > [1] I get
> > the same *REXML* error [2].
> ... [show rest of quote<http://www.nabble.com/Subversion-bundle-problem-td13754459.html#>
> ]
>
> So you can reproduce the error outside TextMate?
>
> > However, if I change it to this (two-liner) it
> > works just fine (of course, it doesn't show in TM...):
> > [...]
> > The error with the rescue block uncommented:
> > /opt/local/lib/ruby/1.8/*rexml*/source.rb:226:in `pos': Illegal seek
> > (Errno::ESPIPE)
>
> It would appear the *REXML* *parser* treats the IO object as more than
> just a pipe (i.e. it tries to seek).
>
> Try instead of using '</tmp/test.log' do: 'cat /tmp/test.log|ruby …',
> see if that changes things. Also try change '2>&1' to '2>/dev/null' in
> the version that fails for you in Terminal.
>
--
Dana
I'm a new TextMate user trying to write a simple bundle command to launch my g++
builds from TextMate. Leaving out the stuff to HTMLify the results (which
doesn't seem to make a difference to this bug), it looks like this:
cd ${TM_PROJECT_DIRECTORY}
./build.sh
Where build.sh is a script which calls make on a series of makefiles, checking
the result each time. It works fine if I call it from the command line. But
when I trigger the command in TextMate, the compiles work fine, but ar calls
("ar crv") to build the library fail pretty consistently with errors like this:
ld: in ../hw_nmtlib_core.a(__debug_frame), not a valid archive member
The error is apparently in the .a file, as executing build.sh from the command
line will still generate the error, until you force it to regenerate the .a file.
I'm hoping someone has an idea what might be going on here, because TextMate
will be a dream if I can get this working properly.
Thanks,
Sol
hi all,
while switiching documents in Latex the following happens.
Hitting the ENTER-key on my keyboard as my cursor is somewhere in the
name of a document (like \input{moretexthere.tex}) results in 'popping-
up' the file 'moretexthere.tex' together with a warning in a yellow
area:
-:14: warning: Insecure world writable dir /Users/.....etc..path...
in PATH, mode 040777
-:18: warning: Insecure world writable dir /Users/.....etc..path...
in PATH, mode 040777
The path stops at a folder where (eventually - 4 subdirectories
deeper) the document I'm working on is located.
Can I improve my settings so that this warning dissappears?
I've seen this mentioned before but couldn't find the thread. My
TextMate.app is located in /Applications and the folder I'm working in
is somewhere in ~/Documents and this all with up to date software and
so on.
Thanks for any reply,
Gert
I was wondering if it was possible to map a key (I'll choose [enter])
to the following procedure:
go to the end of the line (given by a particular column) via tabs and
enter two backslashes and return.
alternatively, if the distance to the given column is less than some
number K, go to the next line, tab over T many tabs, hit two
backslashes and return.
The main use of this for me would be inside the align environment, and
within tables--that way the layout of the align's lines appear
consistent automatically, instead of me having to do it by hand.
Evan
--------------------------------------------------
Cole's Law:
Shredded cabbage goes great with shredded carrots and
mayonnaise.
TextMate suddenly has problems saving files in latin1 encoding (which
I must use if I collaborate with others). Even though TextMate tells
me it saves the file in latin1, upon checking with TextWrangler, it is
clear that they are not saved in the correct format.
The only workaround is to avoid using special characters (like umlaute
or accents). This happens with extremely simple one-file projects as
well as more difficult projects.
Is it possible to downgrade to an older version of TextMate?
Max
Dear All,
I just encountered something of which I think is a bug in the latex bundle.
When using a directory and file structure like this
main.tex
|
---subdir
|
-----submain.tex
|
-----subcontent.tex
where main.tex has an \input{subdir/submain} and submain.tex contains a
\input{subdir/subcontent.tex} the show outline function gives me an error
that the directory
xyz/subdir/subdir/... could not be found (which, as a matter of fact is
correct since it does not exist). To my impression the parser forgets to cut
off the first part of the path in \input{} when in a subdirectory.
For generating a LaTeX file this works fine. Any help or hint would be
greatly appreciated.
Kind regards,
Nima
--
View this message in context: http://www.nabble.com/Latex-Bundle---Bug-in-Show-Outline-tp20909194p2090919…
Sent from the textmate users mailing list archive at Nabble.com.
Is there a way to bind the Home key in a way so that it
behaves similar to UltraEdit?
Nearly 2 years has past, since I last asked about this:
http://thread.gmane.org/gmane.editors.textmate.general/16116
Maybe there is a solution now?
The first time you press Home then the cursor jumps to
the first letter on the line (/^\s*/).
The second time you press Home it jumps to
the beginning of the line (/^/).
position A = ^
position B = ^\s*
Item1. pressing home and cursor jumps to position B.
Item2. except when cursor already is at position B, then it jumps to A.
Item3. doesn't modify the file.
Item4. when shift is held down then it preserves the selection correct.
I have tried different approaches mentioned in the past on
this list, but they have problems with Item3 and Item4.
I have also tried making my own ruby scripts for it, but
there was also problems with Item3 and Item4.
Has anyone a well behaved Smart Home command?
####################################################
# Good: Item1 and Item2
# Bad: Item3 and Item4
#
# Save: Nothing
# Input: Selected Text or Line
# Output: Insert as Snippet
# Activation: Key Equivalent, HomeKeyArrow
# Scope Selector: <blank>
####################################################
#! /usr/bin/ruby
line = ENV['TM_CURRENT_LINE']
index = ENV['TM_LINE_INDEX'].to_i
# extract leading whitespace
remain = line.sub(/(^[ \t]*)/, '')
whitespace = $1
if whitespace == nil
whitespace = ''
elsif index == whitespace.size
whitespace = ''
else
line = remain
end
# escape $ \ `
line.gsub!(/([\$\\`])/){"\\#$1"}
# place cursor
print "#{whitespace}${1}#{line}"
####################################################
--
Simon Strandgaard
my graphics program for mac - http://toolboxapp.com/
None of the Java templates seem to create properly; both from the File-
>New From Template as well as from the the project window...
I haven't gotten the time to look into why yet; but does anyone
already know about this?
-N.
Hi All,
I’m not sure if this has already been addressed, but I noticed
that my CSS language grammar highlights “transparent” in
{background-color: transparent;}, and most everything after that, as
an error (scope = invalid.illegal.css). The more common {background:
transparent;} doesn’t trigger the error, and in that
case “transparent” gets the scope “name =
'support.constant.property-value.css'.” I added transparent to
the value list in “name = 'support.constant.color.w3c-standard-
color-name.css',” which may not be the right place, but works
for me.
peace - oli
> On Fri Dec 5 19:54:25 Simon Strandgaard wrote:
>
>> Is there a way to bind the Home key in a way so that it behaves
>> similar to UltraEdit?
>
> On Fri Dec 5 22:51:55 Oliver Taylor wrote:
>>
>
> (please correct me if I'm wrong)
>
> Don't think it's possible. This is because I don't think TextMate can
> "see" the HOME and END keys being pressed. The OS must intercept the
> keypress and move the view without telling TextMate it even does it.
>
> Maybe a third-part macro utility like Keyboard Maestro could help
> here.
Wow. That was just dumb. Of course TextMate can assign HOME and END to
snippets etc.
What am I? New?
The Markdown bundle:
- Correctly highlights hyphen-delimited bullet lists, and
- Correctly translates hyphen-delimited bullet lists to HTML, but
- Does not allow the writing of such lists! Instead, hyphen-tab creates a horizontal line.
This is a problem because:
- Users may want to use hyhpens to demark bulleted lists instead of asterisks or plus signs for visual reasons
- Users may want to use hyhpens to demark bulleted lists instead of asterisks or plus signs because the hyphen is the only punctuation of those options which does not require use of the Shift button
- This behavior occurs even when converting a paragraph to a bulleted list item (result is "----------[...]---previous paragraph text")
A suggested fix is:
- Force users to type two hyphens for the horizontal-line auto-completion
Thanks,
Alan Hogan
