[TxMt] Re: textmate Digest, Vol 71, Issue 11

David Derbes loki at uchicago.edu
Sat Apr 12 15:12:08 UTC 2014
Previous message: [TxMt] Re: SCM Status pane doesn't show Uncommited Changes
Next message: [TxMt] mate -l does not scroll to selected line
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Apr 9, 2014, at 5:53 AM, <textmate-request at lists.macromates.com> <textmate-request at lists.macromates.com> wrote:

> Send textmate mailing list submissions to
> 	textmate at lists.macromates.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.macromates.com/listinfo/textmate
> or, via email, send a message with subject or body 'help' to
> 	textmate-request at lists.macromates.com
> 
> You can reach the person managing the list at
> 	textmate-owner at lists.macromates.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of textmate digest..."
> 
> 
> Today's Topics:
> 
>   1.  Re: Installing the Cucumber bundle (Leigh Daniels)
>   2.  Re: Issue tracker? (Boris Du?ek)
>   3.  Narrower windows (Quinn Comendant)
>   4.  Re: Narrower windows (Matt Neuburg)
>   5.  No output from python script for one user account but not
>      the others (Nicolas Rougier)
>   6.  Re: No output from python script for one user account but
>      not the others (Allan Odgaard)
>   7.  Re: Narrower windows (Nigel Chapman)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 8 Apr 2014 08:49:03 -0400
> From: "Leigh Daniels" <lcdpublic at comcast.net>
> To: "TextMate users" <textmate at lists.macromates.com>
> Subject: [TxMt] Re: Installing the Cucumber bundle
> Message-ID: <20140408124903.333408250 at smtp.comcast.net>
> Content-Type: text/plain; charset=US-ASCII
> 
> Hi, 
> 
> [Re-sending this because parts were missing.]
> 
> I'm trying to get cucumber working and have tried the previous suggestions to no avail. I'm using the Hello RSpec and Hello Cucumber examples from "The RSpec Book". TextMate: 2.0-alpha.9531 
> 
> If I run the cucumber command in the Terminal, it works but in TextMate I get this: 
> 
> /usr/local/rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- spec (LoadError)
> 	from /usr/local/rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /Users/leigh/Library/Application Support/Avian/Pristine Copy/Bundles/Cucumber.tmbundle/Support/lib/cucumber/mate.rb:31:in `rescue in <top (required)>'
> 	from /Users/leigh/Library/Application Support/Avian/Pristine Copy/Bundles/Cucumber.tmbundle/Support/lib/cucumber/mate.rb:28:in `<top (required)>'
> 	from /usr/local/rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /usr/local/rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /Users/leigh/Library/Application Support/Avian/Pristine Copy/Bundles/Cucumber.tmbundle/Support/lib/cucumber/mate/feature_helper.rb:1:in `<top (required)>'
> 	from /usr/local/rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /usr/local/rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /tmp/cucumber-23006.rb:2:in `<main>'
> 
> Here's the RVM setup: 
> 
> rvm info
> 
> ruby-2.0.0-p247:
> 
>  system:
>    uname:       "Darwin Mingus.local 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64"
>    system:      "osx/10.9/x86_64"
>    bash:        "/bin/bash => GNU bash, version 3.2.51(1)-release (x86_64-apple-darwin13)"
>    zsh:         "/bin/zsh => zsh 5.0.2 (x86_64-apple-darwin13.0)"
> 
>  rvm:
>    version:      "rvm 1.25.22 (stable) by Wayne E. Seguin <wayneeseguin at gmail.com>, Michal Papis <mpapis at gmail.com> [https://rvm.io/]"
>    updated:      "1 minute 9 seconds ago"
>    path:         "/usr/local/rvm"
> 
>  ruby:
>    interpreter:  "ruby"
>    version:      "2.0.0p247"
>    date:         "2013-06-27"
>    platform:     "x86_64-darwin12.3.0"
>    patchlevel:   "2013-06-27 revision 41674"
>    full_version: "ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0]"
> 
>  homes:
>    gem:          "/usr/local/rvm/gems/ruby-2.0.0-p247"
>    ruby:         "/usr/local/rvm/rubies/ruby-2.0.0-p247"
> 
>  binaries:
>    ruby:         "/usr/local/rvm/rubies/ruby-2.0.0-p247/bin/ruby"
>    irb:          "/usr/local/rvm/rubies/ruby-2.0.0-p247/bin/irb"
>    gem:          "/usr/local/rvm/rubies/ruby-2.0.0-p247/bin/gem"
>    rake:         "/usr/local/rvm/gems/ruby-2.0.0-p247/bin/rake"
> 
>  environment:
>    PATH:         "/usr/local/rvm/gems/ruby-2.0.0-p247/bin:/usr/local/rvm/gems/ruby-2.0.0-p247 at global/bin:/usr/local/rvm/rubies/ruby-2.0.0-p247/bin:/usr/local/rvm/bin:/usr/local/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/sm/bin:/opt/sm/pkg/active/bin:/opt/sm/pkg/active/sbin"
>    GEM_HOME:     "/usr/local/rvm/gems/ruby-2.0.0-p247"
>    GEM_PATH:     "/usr/local/rvm/gems/ruby-2.0.0-p247:/usr/local/rvm/gems/ruby-2.0.0-p247 at global"
>    MY_RUBY_HOME: "/usr/local/rvm/rubies/ruby-2.0.0-p247"
>    IRBRC:        "/usr/local/rvm/rubies/ruby-2.0.0-p247/.irbrc"
>    RUBYOPT:      ""
> 
> Thanks for any suggestions. 
> 
> **Leigh 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 8 Apr 2014 22:19:33 +0200
> From: Boris Du?ek <me at dusek.me>
> To: TextMate users <textmate at lists.macromates.com>
> Subject: [TxMt] Re: Issue tracker?
> Message-ID: <69374DB4-CB1B-4361-80C3-2F590B576A54 at dusek.me>
> Content-Type: text/plain; charset=windows-1252
> 
>>> Will the github issues come back? Or is still the best way for some user who wants to report accessibility bugs to write to the textmate mailing list? Or to the textmate-dev mailing list?
>> 
>> If the user is OK with mailing lists, then this list is fine (textmate-dev is sort of a legacy list that I am considering shutting down), otherwise one can write support or try IRC (where I am often available).
>> 
>> I?m not sure if GitHub Issues will be back, it felt like an unwanted chore, and as people can still submit bug reports or suggest features, the loss of the issue tracker is IMHO negligible ? the main advantage people tend to claim is that one can search through existing issues, nonetheless I closed issues as duplicates daily, so in practice few used that feature, and was just burdening me with administrative work that was hard to outsource (and adding more noise to the issue tracker that degraded the searching experience).
>> 
>> If you?re asking from the POV of a contributor, i.e. how can you be made aware of accessibility issues, then we can relay issues reported.
> 
> Please feel free to relay to me any accessibility issues reported by any channel (except this mailing list which I follow) to you.
> 
> I was asking about GitHub issues because I myself prefer some tracker like that. I like to be able to write down issues when they occur to me or anyone else, review the issue list from time to time, close issues as they get fixed etc. E.g. right now I have at least 2 issues that I am keeping in my head :-) and will not be fixing them right away.
> 
> But another idea occurred to me - maybe I could then open GitHub issues on my fork of textmate (https://github.com/dusek/textmate/) and mark it as only for accessibility (I already preemptively did that with the fork page title). As the issue topic would be limited to accessibility, closing duplicates would probably not be such a burden (and would be done by me :-)
> 
> If you have no objection to that, I would then open the Issues on my fork as that would be the way I would prefer to keep track of accessibility issues. If someone submitted something to the list (or it was relayed to me), I would simply put it in that tracker to not forget it and be able to get back to it sometime. Then README.md on textmate/textmate could get updated to point to the dusek/textmate issues for accessibility issues only.
> 
> Would that be OK with you?
> 
>> We can also do a new mailing list for people who use the accessibility features. This would also allow soliciting feedback about the current accessability support and make more detailed announcements about the changes being done to improve it.
> 
> I am not sure that is such a great idea as it might sound at first (mainly for the philosophical reason that since accessibility should be an integral part of a product, accessibility discussions should IMHO be an integral part of the main user mailing list). But I also see the practical advantages you are mentioning. Half of me is for it, half of me is against it - let me think about it for a few days more :-)
> 
> Thanks,
> Boris
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 8 Apr 2014 19:37:20 -0500
> From: Quinn Comendant <quinn at strangecode.com>
> To: TextMate users <textmate at lists.macromates.com>
> Subject: [TxMt] Narrower windows
> Message-ID: <20140408193720967803.b24565ee at strangecode.com>
> Content-Type: text/plain; charset=iso-8859-1
> 
> I'd like to put my 2? towards allowing TM2 windows to shrink narrower than what now appears to be a ~ 538px minimum limit. It is sometimes nice to have a narrow window next to a much wider window. I don't remember TM1 having this min limit. It seems TM2's min width is determined by the status and menus a the bottom-left of the window.
> 
> This became an issue for me because a) now using a "13 MBA, and b) have found the wonderful <http://spectacleapp.com/> to allow hotkey-window resizing. One of the dimensions Spectacle supports is too narrow for TM2, and blocks easy automated window tiling. =)
> 
> -- 
> Quinn Comendant
> Strangecode, LLC
> http://www.strangecode.com/
> @qc and @strangecode
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 8 Apr 2014 18:32:14 -0700
> From: Matt Neuburg <matt at tidbits.com>
> To: TextMate users <textmate at lists.macromates.com>
> Subject: [TxMt] Re: Narrower windows
> Message-ID: <0498AE19-AFC9-4B69-8577-8BEFE8BB3E8A at tidbits.com>
> Content-Type: text/plain; charset=iso-8859-1
> 
> 
> On Apr 8, 2014, at 5:37 PM, Quinn Comendant <quinn at strangecode.com> wrote:
> 
>> I'd like to put my 2? towards allowing TM2 windows to shrink narrower than what now appears to be a ~ 538px minimum limit. It is sometimes nice to have a narrow window next to a much wider window. I don't remember TM1 having this min limit. It seems TM2's min width is determined by the status and menus a the bottom-left of the window.
>> 
>> This became an issue for me because a) now using a "13 MBA
> 
> I have a 13-inch MacBook (Pro), and what I do is to show document tabs even for a single document, with command output to the right of text view. Every script I open thus becomes a tab in this one window, and I say New Tab when I want to make a completely new script. Thus there is just one window! It's true I can't see two scripts at once, but I don't need to; I can see a script and its results, and that's what matters. I could make this single window full-screen, but I don't usually bother.
> 
> I'm not saying this would work for your purposes, but personally, when I discovered I could work like this on the small screen, I was really happy. 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
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Wed, 9 Apr 2014 12:04:55 +0200
> From: Nicolas Rougier <Nicolas.Rougier at inria.fr>
> To: textmate at lists.macromates.com
> Subject: [TxMt] No output from python script for one user account but
> 	not	the others
> Message-ID: <BD17357E-92CB-439C-B2AD-9C44DAC8F2AC at inria.fr>
> Content-Type: text/plain; charset=us-ascii
> 
> 
> Hi,
> 
> I'm using the latest version (2.0-alpha.9529) and I've some problems getting python output when running the script.
> 
> The python script is just:
> 
> print "ok"
> 
> 
> It works fine when ran in terminal (Run Script (Terminal)) but if I run script directly (Run Script), I get no output. For other type of files (Latex for example), everything seems ok.
> 
> 
> The weirdest part is that if I do the same with another user (administrator) it works fine and I get the output in the window: from my regular account, I can "su administrator" and starts TM from command line and it works as expected.
> 
> I tried to reinstall TM, not load my .profile/.bashrc in case something's wrong in my path, delete any TM preferences (com.macromates.TextMate.preview and Library/Caches/...) but it does no change anything.
> 
> 
> So I guess something wrong's  with my regular account but I'm out of ideas at this point.
> (I also checked "env" gives same values for regular/administrator)
> 
> 
> If someone has any idea ... or how to debug.
> 
> 
> 
> Nicolas
> 
> ------------------------------
> 
> Message: 6
> Date: Wed, 09 Apr 2014 17:44:11 +0700
> From: "Allan Odgaard" <mailinglist at textmate.org>
> To: "TextMate users" <textmate at lists.macromates.com>
> Subject: [TxMt] Re: No output from python script for one user account
> 	but not the others
> Message-ID: <59CEE812-97CC-459D-96EA-4C9A7E842499 at textmate.org>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 9 Apr 2014, at 17:04, Nicolas Rougier wrote:
> 
>> [?] if I run script directly (Run Script), I get no output.
> 
> What does ?no output? mean? Is the action a no-op, i.e. no windows 
> showing?
> 
> If so, try Preferences ? Bundles and uncheck/check the Python bundle.
> 
> There is an issue with updating bundles (in current release build) where 
> if TM is terminated while updating a bundle, it can leave a broken 
> bundle on disk (partially deleted), which could manifest itself as some 
> actions being no-op (although deleting ~/Library/Caches should have made 
> deleted actions disappear from the menu).
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Wed, 9 Apr 2014 11:53:36 +0100
> From: Nigel Chapman <nigel at macavon.co.uk>
> To: TextMate users <textmate at lists.macromates.com>
> Subject: [TxMt] Re: Narrower windows
> Message-ID: <F3C29074-33F0-4B3E-924C-96537842DB9B at macavon.co.uk>
> Content-Type: text/plain; charset="windows-1252"
> 
> Split pane windows would solve this problem. I just had a look at Bounty Source (https://www.bountysource.com/issues/27-split-pane-feature) and it would seem that there?s somebody willing to pick up the issue if another $16 is raised.
> 
> 
> On 9 Apr 2014, at 01:37, Quinn Comendant <quinn at strangecode.com> wrote:
> 
>> I'd like to put my 2? towards allowing TM2 windows to shrink narrower than what now appears to be a ~ 538px minimum limit. It is sometimes nice to have a narrow window next to a much wider window. I don't remember TM1 having this min limit. It seems TM2's min width is determined by the status and menus a the bottom-left of the window.
>> 
>> This became an issue for me because a) now using a "13 MBA, and b) have found the wonderful <http://spectacleapp.com/> to allow hotkey-window resizing. One of the dimensions Spectacle supports is too narrow for TM2, and blocks easy automated window tiling. =)
>> 
>> -- 
>> Quinn Comendant
>> Strangecode, LLC
>> http://www.strangecode.com/
>> @qc and @strangecode
>> 
>> 
>> _______________________________________________
>> textmate mailing list
>> textmate at lists.macromates.com
>> http://lists.macromates.com/listinfo/textmate
> 
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 2776 bytes
> Desc: not available
> URL: <http://lists.macromates.com/textmate/attachments/20140409/8cb7fdf8/attachment.p7s>
> 
> ------------------------------
> 
> _______________________________________________
> textmate mailing list
> textmate at lists.macromates.com
> http://lists.macromates.com/listinfo/textmate
> 
> End of textmate Digest, Vol 71, Issue 11
> ****************************************
Previous message: [TxMt] Re: SCM Status pane doesn't show Uncommited Changes
Next message: [TxMt] mate -l does not scroll to selected line
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the textmate mailing list