I've just noticed that template for XHTML/1.1 has been changed to include
application/xhtml+xml content type in <meta> element.
This is completly misguided as <meta> is there only for
backwards-compatibility non-XHTML user-agents -- that is only those which
*do not* support application/xhtml+xml.
From W3C XHTML FAQ:
"Note that a meta http-equiv statement will not be recognized by XML
processors, and authors SHOULD NOT include such a statement in an XHTML
document served as 'application/xml' (and 'application/xhtml+xml' as well
for that matter)."
Please change it back to text/html or remove <meta> element completly.
--
regards, porneL
hello
With a a latex file the commands of textmate : create a html file and
creta a css file don't work
tm_dialog_v5: invalid option -- a
tm_dialog r6021 (2006-11-16)
Usage: tm_dialog [-cmqp] nib_file
Usage: tm_dialog [-p] -u
Options:
-c, --center Center the window on screen.
-d, --defaults <plist> Register initial values for user defaults.
-m, --modal Show window as modal.
-q, --quiet Do not write result to stdout.
-p, --parameters <plist> Provide parameters as a plist.
-u, --menu Treat parameters as a menu structure.
tm_dialog: you have updated the Dialog plug-in to v7 but the
tm_dialog tool is still at v5
/Applications/TextMate.app/Contents/SharedSupport/Support/lib/
dialog.rb:53:in `initialize': No such dialog ()
(TextMate::WindowNotFound)
} for command: /Applications/TextMate.app/Contents/SharedSupport/
Support/bin/tm_dialog -a -c -p \<\?xml\ version\=\"1.0\"\ encoding\=
\"UTF-8\"\?\>'
'\<\!DOCTYPE\ plist\ PUBLIC\ \"-//Apple\ Computer//DTD\ PLIST\ 1.0//EN
\"\ \"http\://www.apple.com/DTDs/PropertyList-1.0.dtd\"\>'
'\<plist\ version\=\"1.0\"\>'
'\<dict\>'
'\ \<key\>details\</key\>'
'\ \<string\>\</string\>'
'\ \<key\>isIndeterminate\</key\>'
'\ \<true/\>'
'\ \<key\>summary\</key\>'
'\ \<string\>Creating\ HTML\ version\ of\ selection…\</string\>'
'\ \<key\>title\</key\>'
'\ \<string\>Progress\</string\>'
'\</dict\>'
'\</plist\>'
' ProgressDialog.nib from /Applications/TextMate.app/Contents/
SharedSupport/Support/lib/dialog.rb:26:in `new'
from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/
dialog.rb:26:in `dialog'
from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/
progress.rb:40:in `call_with_progress'
from /tmp/temp_textmate.h1501H:5
and with create a css
/Users/ego/Library/Application Support/TextMate/Bundles/
TextMate.tmbundle/Support/lib/doctohtml.rb:47:in `require': No such
file to load -- /Applications/TextMate.app/Contents/SharedSupport/
Support/lib/plist (LoadError)
from /Users/ego/Library/Application Support/TextMate/Bundles/
TextMate.tmbundle/Support/lib/doctohtml.rb:47:in
`generate_stylesheet_from_theme'
from /tmp/temp_textmate.hIcEvZ:3
Alain
Hi all, I just downloaded the update to TextMate and my `new environment
based on current word' seems to have been broken: command { gives
/Library/Application
Support/TextMate/Bundles/Latex.tmbundle/Support/lib/config_helper.rb:1:in
/bin/bash: -c: line 1: unexpected EOF while looking for matching `''
/bin/bash: -c: line 4: syntax error: unexpected end of filerequire'
from /tmp/temp_textmate.xBSaAH:4
It worked before. The new command code is:
#!/usr/bin/env ruby
SUPPORT = ENV['TM_BUNDLE_SUPPORT']
require ENV['TM_SUPPORT_PATH'] + '/lib/dialog'
require SUPPORT + '/lib/config_helper.rb'
@plist = Config.load
shortcuts = @plist['environments']
lshortcuts = @plist['labeled_environments']
if ENV['TM_SCOPE'].match('beamer') then
shortcuts.update(@plist['environments_beamer'])
lshortcuts.update(@plist['labeled_environments_beamer'])
end
name = STDIN.read
cmd = nil
if name == "" then
arr = ["custom…",nil] + (shortcuts.keys+lshortcuts.keys).sort
ind = Dialog.menu(arr)
if ind.nil? || ind == 0 then
name = ""
else
name = arr[ind]
end
end
for key in shortcuts.keys do
if shortcuts[key]['triggers'].index(name) then
cmd = key
setting = :no_label
dict = shortcuts
end
end
for key in lshortcuts.keys do
if lshortcuts[key]['triggers'].index(name) then
cmd = key
setting = :label
dict = lshortcuts
end
end
if !cmd.nil? then
print "\\begin{#{cmd}}"
print "\n" if setting == :no_label
print dict[cmd]["content"] || "\t$0"
print "\n\\end{#{cmd}}"
elsif name == ""
print "\\begin{${1:env}}\n\t$0\n\\end{${1:env}}"
else
print "\\begin{#{name}}\n\t$0\n\\end{#{name}}"
end
Thanks,
Anand Patil
Hi
I have changed
\s+
by
\s*
in the (L)anguage grammar for to C recognize also "name(args)" and
not only "name (args)" as function prototype in C.
I did easily the change in the C bundle, but my question es:
is it the best way of changing an standard bundle?
if that bundle is updated in the future by the TM developers, will
it be updated in my system?
Thanks
On Feb 27, 2007, at 9:14 AM, Allan Odgaard wrote:
> Could you btw make a case for the new Ruby syntax? I never figured
> out what problem it was supposed to solve.
The default Ruby syntax doesn't scope enough stuff.
There are very basic things that are completely missing like
method calls, operators and lambda variables.
My Ruby Experimental adds these basic things and a few other niceties
like leading space and core library method names and better
punctuation support.
The advantage is partly for the ability to better theme Ruby files,
which many people like myself are looking at all day every day.
Looking at mostly white on black text all day is enough to make you
go mad.
Another advantage is in using the Select Scope command to better and
more quickly select the current relevant scope.
When you don't know the language as well as you'd like, having the
core library methods colored slightly differently can really help you
to quickly notice any misspellings and such.
So, to sum up:
finish scoping the basic syntax of the language
different kinds of operators, methods, lambda variables, basic
punctuation like the => thing, etc…
core methods
Improved text interaction with select scope
improved readability with leading space scopes
improved awesomeness with the minimization of unscoped generic text
But, that's not really the point.
The point is that a syntax should scope as much as possible, not as
little as necessary.
Then it's up to each person to choose how you use those scopes.
Just take a bit of a peek for yourselves internet people!
Would you rather spend all day looking at this:
http://flickr.com/photo_zoom.gne?
id=404629435&context=photostream&size=o
or this?
http://flickr.com/photo_zoom.gne?
id=404629540&context=photostream&size=o
(if you hate that theme, just pretend you love it instead)
thomas Aylott — subtleGradient — CrazyEgg — sixteenColors
Yep, Allan,
that did it.
sorry for reading only parts...
Thanks,
Claus
On 5-Mar-07, at 1:00 PM, textmate-request(a)lists.macromates.com wrote:
> From: Allan Odgaard <throw-away-1(a)macromates.com>
>
>
> Please see http://macromates.com/textmate/manual/
> bundles#setting_lc_ctype
Haris,
unfortunately, it still doesn't work for me to install the R bundle.
Here are the logs I get:
svn co http://macromates.com/svn/Bundles/trunk/Bundles/R.tmbundle/
A R.tmbundle/Commands
A R.tmbundle/Commands/Vector.tmCommand
A R.tmbundle/Commands/Show in R help.tmCommand
A R.tmbundle/Commands/Command Usage.tmCommand
A R.tmbundle/Commands/Wrap Selection in Function Call.tmCommand
subversion/libsvn_subr/utf.c:466: (apr_err=22)
svn: Can't convert string from 'UTF-8' to native encoding:
subversion/libsvn_subr/utf.c:464: (apr_err=22)
svn: R.tmbundle/Commands/Plots?\226?\128?\166.tmCommand
I don't really know what this could mean... but I'd appreciate any help!
Thanks,
Claus
On 4-Mar-07, at 10:04 PM, textmate-request(a)lists.macromates.com wrote:
> I added a new syntax file for Rd documentation, and forgot to also
> commit the info.plist file. Perhaps that was the problem? I just
> committed it, so try to svn up and tell me if you still have
> problems with it.
>
> Haris Skiadas
> Department of Mathematics and Computer Science
> Hanover College
Is there some way to make TextMate not open documents that were last
open? For some reason - when editing files over FTP especially - it
likes to re-open a bunch of old documents, so I have to apple-W a
bunch of documents before apple-Q'ing.
Any way to do this?
--
Wells Oliver
wells.oliver(a)gmail.com
I'm getting the following stack trace when I select the 'Install Plugin'
command in the Rails bundle:
/Users/scott/Library/Application Support/TextMate/Pristine
Copy/Bundles/Rails.tmbundle/Support/lib/rails/text_mate.rb:69:in
`method_missing': undefined method `filepath' for TextMate:Module
(NoMethodError) from /Users/scott/Library/Application
Support/TextMate/Pristine
Copy/Bundles/Rails.tmbundle/Support/lib/rails/rails_path.rb:43:in
`initialize' from /Users/scott/Library/Application Support/TextMate/Pristine
Copy/Bundles/Rails.tmbundle/Support/bin/list_plugins.rb:25:in `new' from
/Users/scott/Library/Application Support/TextMate/Pristine
Copy/Bundles/Rails.tmbundle/Support/bin/list_plugins.rb:25
I'm using 'cuting edge' Textmate 1.5.4 (1360). I've attempted this with both
the distributed Rails bundle, and the version in svn (via the GetBundle
bundle).
I'm running ruby version 1.8.5 (2006-12-25 patchlevel 12) [i686-darwin8.8.1],
installed via mac ports. I'm running Rails 1.2.2.
My apologies if this is already answered in the mailing lists; I couldn't
find any mention of this in the march or february archies, and a few
different google searches involving 'filepath textmate' don't bring back
anything interesting.
Many thanks for your help.
-Scott
