9 Nov
2014
9 Nov
'14
2:28 a.m.
Is there any documentation of changes needed to convert 1.5 bundles to work with 2.0? I
dragged the 1.5 bundle to TextMate 2 and it asks if I want to install it. Click OK and
nothing seems to happen. The bundle is not installed and no errors on the screen or in the
log.
Thanks,
John DeSoi, Ph.D.
9 Nov
9 Nov
3:27 p.m.
On 9 Nov 2014, at 3:28, John DeSoi wrote:
Is there any documentation of changes needed to
convert 1.5 bundles to
work with 2.0?
No conversion should be necessary.
Though if it’s an old bundle that uses ruby, then upgrading to
Yosemite may require updating shebangs.
I dragged the 1.5 bundle to TextMate 2 and it asks if
I want to
install it. Click OK and nothing seems to happen. The bundle is not
installed and no errors on the screen or in the log.
Does it not show up in the bundle editor?
Is the bundle online somewhere (so that we could try to reproduce)?
7:10 p.m.
On Nov 9, 2014, at 9:27 AM, Allan Odgaard <mailinglist(a)textmate.org> wrote:
No, nothing shows up in the bundle editor for it. You can download it here:
http://pgedit.com/public/pgedit/pgEdit_TextMate_2.1.zip
or on github:
https://github.com/desoi/pgedit-textmate
I'm using Textmate 2.0b6.
Thanks,
John DeSoi, Ph.D.
I dragged the
1.5 bundle to TextMate 2 and it asks if I want to install it. Click OK and nothing seems
to happen. The bundle is not installed and no errors on the screen or in the log.
Does it not show up in the bundle editor?
Is the bundle online somewhere (so that we could try to reproduce)?
11 Nov
11 Nov
7:29 a.m.
On 9 Nov 2014, at 20:10, John DeSoi wrote:
Thanks, the issue is that the bundle contains a titlecased
“Info.plist” where TextMate 2.0 only looks for the lowercased
version (“info.plist”).
For now you can rename the contained “Info.plist” (to be lowercase)
but I’ll make TextMate ignore the case of the file starting with next
build.
Is the bundle
online somewhere (so that we could try to reproduce)?
[…]
https://github.com/desoi/pgedit-textmate 
2:46 p.m.
On Nov 10, 2014, at 11:29 PM, Allan Odgaard <mailinglist(a)textmate.org> wrote:
Thanks, the issue is that the bundle contains a titlecased “Info.plist” where TextMate
2.0 only looks for the lowercased version (“info.plist”).
Then TextMate 2.0 is wrong.
For now you can rename the contained “Info.plist” (to
be lowercase) but I’ll make TextMate ignore the case of the file starting with next
build.
No, it shouldn't "ignore the case". It should look for titlecased
"Info.plist" - to match what Apple looks for:
https://developer.apple.com/library/mac/documentation/CoreFoundation/Concep…
It happens that your lowercase "info.plist" might work on some people's
machines, but you cannot rely on this: a folder that contains a lowercase
"info.plist" can break against Apple's expectations, and this thing will
then appear as a normal folder in the Finder, not a bundle. You should not _accept_
Info.plist; you should _require_ Info.plist, just like Apple.
m.
--
matt neuburg, phd = http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
3:26 p.m.
On 11 Nov 2014, at 15:46, Matt Neuburg wrote:
It happens that your lowercase "info.plist"
might work on some
people's machines, but you cannot rely on this: a folder that contains
a lowercase "info.plist" can break against Apple's expectations […]
TextMate bundles are *not* following the format of an
application/framework bundle.
For example in an application/framework bundle the Info.plist is placed
in a subfolder named “Contents” which is not the case for TextMate
bundles.
So TextMate is not wrong, it follows the standard I did 10 years ago
*inspired* by Apple, but with the info.plist in lowercase (and at the
root level of the bundle).
I later made TextMate 1.x accept Info.plist as well, but from day one,
the standard was info.plist, and that is what I carried over to 2.0.
3:51 p.m.
That's odd, because the version of TextMate.app I have installed,
2.0-beta.6, shows a Contents folder containing an Info.plist file, just
like all my other apps. I don't see an info.plist file anywhere.
On Tue, Nov 11, 2014 at 10:26 AM, Allan Odgaard <mailinglist(a)textmate.org>
wrote:
On 11 Nov 2014, at 15:46, Matt Neuburg wrote:
It happens that your lowercase "info.plist" might work on some people's
machines, but you cannot rely on this: a folder
that contains a lowercase
"info.plist" can break against Apple's expectations […]
TextMate bundles are *not* following the format of an
application/framework bundle.
For example in an application/framework bundle the Info.plist is placed in
a subfolder named “Contents” which is not the case for TextMate bundles.
So TextMate is not wrong, it follows the standard I did 10 years ago
*inspired* by Apple, but with the info.plist in lowercase (and at the root
level of the bundle).
I later made TextMate 1.x accept Info.plist as well, but from day one, the
standard was info.plist, and that is what I carried over to 2.0.
_______________________________________________
textmate mailing list
textmate(a)lists.macromates.com
http://lists.macromates.com/listinfo/textmate
4:16 p.m.
On 11 Nov 2014, at 16:51, jomali wrote:
That's odd, because the version of TextMate.app I
have installed,
2.0-beta.6, shows a Contents folder containing an Info.plist file,
just
like all my other apps. I don't see an info.plist file anywhere.
We’re talking about the bundles, not the application.
Look in ~/Library/Application Support/TextMate/Managed/Bundles and
select “Show Package Contents”. There you will find no
“Contents” folder and all of the root level property lists are named
“info.plist”.
4:17 p.m.
On Nov 11, 2014, at 7:26 AM, Allan Odgaard <mailinglist(a)textmate.org> wrote:
TextMate bundles are *not* following the format of an
application/framework bundle.
Oh, I see. So it is not a bundle in that sense. Sorry about that. m.
--
matt neuburg, phd = http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
4:43 p.m.
On Nov 11, 2014, at 1:29 AM, Allan Odgaard <mailinglist(a)textmate.org> wrote:
Thanks, the issue is that the bundle contains a
titlecased “Info.plist” where TextMate 2.0 only looks for the lowercased version
(“info.plist”).
For now you can rename the contained “Info.plist” (to be lowercase) but I’ll make
TextMate ignore the case of the file starting with next build.
Thanks, I was hoping it was something simple.
Interesting that Apple wants it to be an uppercase "I". I tried changing it in
the Finder directly and with the Get Info dialog. It reverted back to uppercase. I had to
use mv in Terminal.
John DeSoi, Ph.D.
5 Feb
5 Feb
3:29 a.m.
On Nov 11, 2014, at 10:43 AM, John DeSoi
<desoi(a)pgedit.com> wrote:
On Nov 11, 2014, at 1:29 AM, Allan Odgaard <mailinglist(a)textmate.org> wrote:
I upgraded to version 2.0-beta.6.8 last night but it still won't work with Info.plist.
I would be happy to just change it in the git repository, but I'm not seeing how to do
that. I tried
$ git mv Info.plist info.plist
fatal: destination exists, source=pgEdit.tmbundle/Info.plist,
destination=pgEdit.tmbundle/info.plist
Do I have to delete it first and add it again? I was trying to just wait until it worked
with the current release so I would not have to change it :).
Thanks,
John DeSoi, Ph.D.
Thanks, the issue is that the bundle contains a
titlecased “Info.plist” where TextMate 2.0 only looks for the lowercased version
(“info.plist”).
For now you can rename the contained “Info.plist” (to be lowercase) but I’ll make
TextMate ignore the case of the file starting with next build.
Thanks, I was hoping it was something simple.
Interesting that Apple wants it to be an uppercase "I". I tried changing it in
the Finder directly and with the Get Info dialog. It reverted back to uppercase. I had to
use mv in Terminal.
3:40 a.m.
On Feb 4, 2015, at 7:29 PM, John DeSoi <desoi(a)pgedit.com> wrote:
$ git mv Info.plist info.plist
fatal: destination exists, source=pgEdit.tmbundle/Info.plist,
destination=pgEdit.tmbundle/info.plist
Do I have to delete it first and add it again?
No, I expect you can just do
$ git mv Info.plist foo.plist
$ git mv foo.plist info.plist
You have to work around the fact that your file system is case-insensitive, that's all
(so that Info.plist and info.plist are seen as identical). m.
--
matt neuburg, phd = http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 8! http://shop.oreilly.com/product/0636920034261.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
2257
days inactive
2345
days old
12 comments
4 participants
participants (4)
-
Allan Odgaard -
John DeSoi -
jomali -
Matt Neuburg