[#17566] rubychecker - runs checks on a Ruby interpreter — Igal Koshevoy <igal@...>

I've put together a shell script that runs checks on a Ruby interpreter.

14 messages 2008/07/03

[#17615] [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...>

At the moment, ruby-mode.el uses font-lock-keywords as opposed to

22 messages 2008/07/05
[#17657] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Yukihiro Matsumoto <matz@...> 2008/07/08

[#17678] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/09

It was designed to fix the following case:

[#17755] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/13

Here's a third patch that fixes a bug in the second and uses a quicker

[#17772] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/15

One more patch which fixes a few bugs in the the last one.

[#17773] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nobuyoshi Nakada <nobu@...> 2008/07/15

Hi,

[#17776] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/15

Looks like version 22 doesn't support explicitly numbered regexp groups.

[#17779] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nobuyoshi Nakada <nobu@...> 2008/07/15

Hi,

[#17783] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nobuyoshi Nakada <nobu@...> 2008/07/15

Hi,

[#17788] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/15

Alright, here's a version that fixes both the highlighting bug and the

[#17793] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nobuyoshi Nakada <nobu@...> 2008/07/16

Hi,

[#17644] Features to be included in Ruby 1.9.1 — "Yugui (Yuki Sonoda)" <yugui@...>

Hi, all

27 messages 2008/07/08

[#17674] [Ruby 1.8 - Bug #238] (Open) Ruby doesn't respect the Windows read-only flag — Jim Deville <redmine@...>

Issue #238 has been reported by Jim Deville.

10 messages 2008/07/08

[#17708] [Ruby 1.8 - Bug #252] (Open) Array#sort doesn't respect overridden <=> — Ryan Davis <redmine@...>

Issue #252 has been reported by Ryan Davis.

13 messages 2008/07/09

[#17871] duping the NilClass — "Nasir Khan" <rubylearner@...>

While nil is an object, calling dup on it causes TypeError. This doesnt seem

33 messages 2008/07/20
[#17872] Re: duping the NilClass — Urabe Shyouhei <shyouhei@...> 2008/07/20

Nasir Khan wrote:

[#17873] Re: duping the NilClass — "Meinrad Recheis" <meinrad.recheis@...> 2008/07/20

On Sun, Jul 20, 2008 at 7:55 PM, Urabe Shyouhei <shyouhei@ruby-lang.org>

[#17877] Re: duping the NilClass — Urabe Shyouhei <shyouhei@...> 2008/07/20

Meinrad Recheis wrote:

[#17879] Re: duping the NilClass — Kurt Stephens <ks@...> 2008/07/20

Urabe Shyouhei wrote:

[#17880] Re: duping the NilClass — "Nasir Khan" <rubylearner@...> 2008/07/21

I write a lot of hand crafted dup or clone because I want control as well as

[#17881] Re: duping the NilClass — "David A. Black" <dblack@...> 2008/07/21

Hi --

[#17882] Re: duping the NilClass — Urabe Shyouhei <shyouhei@...> 2008/07/21

+1 to David. A convenient way to do Marshal idiom should be a new

[#17885] Re: duping the NilClass — "Robert Dober" <robert.dober@...> 2008/07/21

On Mon, Jul 21, 2008 at 8:21 AM, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:

[#17887] Re: duping the NilClass — "David A. Black" <dblack@...> 2008/07/21

Hi --

[#17889] Re: duping the NilClass — "Robert Dober" <robert.dober@...> 2008/07/21

On Mon, Jul 21, 2008 at 1:02 PM, David A. Black <dblack@rubypal.com> wrote:

[#17883] [Ruby 1.9 - Bug #340] (Open) 1.9/trunk does not work when compiled with llvm-gcc4 2.3 (gcc 4.2.1) — Ollivier Robert <redmine@...>

Issue #340 has been reported by Ollivier Robert.

14 messages 2008/07/21

[#17943] RUBY_ENGINE? — "Vladimir Sizikov" <vsizikov@...>

Hi,

56 messages 2008/07/24
[#17950] Re: RUBY_ENGINE? — Tanaka Akira <akr@...> 2008/07/25

In article <3454c9680807241200xf7cc766qb987905a3987bb78@mail.gmail.com>,

[#17958] Re: RUBY_ENGINE? — "Vladimir Sizikov" <vsizikov@...> 2008/07/25

Hi,

[#17981] Re: RUBY_ENGINE? — Tanaka Akira <akr@...> 2008/07/26

In article <3454c9680807250054i70db563duf44b42d92ba41bfb@mail.gmail.com>,

[ruby-core:17874] Re: Expand_Path: New Patch - Modified Processing

From: "C.E. Thornton" <admin@...>
Date: 2008-07-20 18:36:22 UTC
List: ruby-core #17874
Hi,
  Your patch is much cleaner than mine, good job.

   It is not a failure of user name!

   If the directory contains a dir named '~test', it is
a perfectly acceptable dir name.  As long as the 'name'
part of  '~name' is NOT a user name, it should be valid!

 Lets look at how BASH Processes these directories:

      cd ~chuck     (A user name on my system)
          returns /home/chuck  
      cd ~test         (test is NOT a user name on my system)
          returns 'current_dir/~test'    <== Why should this produce an 
error?

  As my previous Example.  I have a directory as follows:

            hydra(Wpad02}$pwd;ls
            /home/thornton/WorkPads/Wpad02
            ATTIC  ~chuck  file_scan.rb  md5_compare.rb  ~test  tst.rb
            hydra(Wpad02}$

             'ATTIC'  '~chuck'  and  '~test'  are directories!

The result with either your change or mine with 'tst.rb'

            ruby 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]
            Starting Directory = .
            Dir = /home/thornton/WorkPads/Wpad02/~test
            Dir = /home/thornton/WorkPads
            Dir = /home/thornton/WorkPads/Wpad02/ATTIC
            Dir = /home/thornton/WorkPads/Wpad02
            Dir = /home/chuck
            hydra(Wpad02}$


ATTIC and ~test are legitimate and should be processed.
~chuck is unreachable without quoting and this is correct
since there is a user named 'chuck'.

NOW, I myself would not consider applying ~name conversion
for any user accept the current user, but BASH does otherwise.

I am simply trying to align expand_path to the way linux (BASH)
processes these names.

I look forward to you response.   I am retired and generally work
late a night USA time, so you should be able to catch during your
day if we  are lucky.

 Chuck T.




  
> Hi,
>
> At Sun, 20 Jul 2008 05:52:07 +0900,
> C.E. Thornton wrote in [ruby-core:17865]:
>   
>>   I modified file.c to incorporated previous suggestions
>> and my mistaken interpretation of Bash Semantics.
>>     
>
> This is my patch, though still I'm not sure if it should ignore
> the failure of user name.
>
> 
> Index: file.c
> ===================================================================
> --- file.c	(revision 18135)
> +++ file.c	(working copy)
> @@ -2649,5 +2649,6 @@ file_expand_path(VALUE fname, VALUE dnam
>  	    if (!pwPtr) {
>  		endpwent();
> -		rb_raise(rb_eArgError, "user %s doesn't exist", buf);
> +		s = --b;
> +		goto relative;
>  	    }
>  	    dirlen = strlen(pwPtr->pw_dir);
> @@ -2697,4 +2698,5 @@ file_expand_path(VALUE fname, VALUE dnam
>  #endif
>      else if (!is_absolute_path(s)) {
> +      relative:
>  	if (!NIL_P(dname)) {
>  	    file_expand_path(dname, Qnil, result);
> 
>
>   


-- 
Competency and chastity have much in common,
they both encompass their own punishment! 
 
-- C.E. Thornton -- Hawthorne Press --


In This Thread