hgignore parser should start in regexp mode to match hgs behaviour
Reported by Henning Schild | March 25th, 2011 @ 02:53 PM
Just try this:
cd /tmp/ mkdir foo cd foo/ touch hello world echo '^he' > .hgignore hg init
now compare
amp st hg st
trivial patch to fix this:
--- a/lib/amp/support/mercurial/ignore.rb Sun Aug 08 00:01:27 2010
-0400 +++ b/lib/amp/support/mercurial/ignore.rb Fri Mar 25 15:49:24
2011 +0100 @@ -71,7 +71,7 @@
# @return [Array<Regexp>] the regexps generated from the strings and syntaxes
def matcher_for_text(text)
return [] unless text
-
syntax = nil -
syntax = :regexp lines = parse_lines(text).reject {|line| line.empty? } # take the lines and create a new array of the patterns
Comments and changes to this ticket
-

Henning Schild March 25th, 2011 @ 03:03 PM
mhh what a formatting mess, so ill try again
get a simple repo with a simple ignore-file
cd /tmp/
mkdir foo
cd foo/
touch hello world
echo '^he' > .hgignore
hg initnow compare
hg st
amp stpatch is attached, would not even show up right in a
span
sorry but who needs wiki syntax a bug tracker?
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Rethink Version Control.- http://amp.carboni.ca/
Amp aims to put control of version-control software in your hands as a developer. The entire system is written in Ruby (with C extensions to improve performance), and aims to implement all major VCS's in Ruby. Currently, Mercurial is implemented.
Other features:
Commands are first-class members of the system - drop in an "Ampfile" in your repository, and you can add commands to amp in the same manner you add commands to rake (only with far, far more power!)
Documentation is one of our biggest priorities. We require all methods to be documented - even comically simple ones.
Heavy testing.
Multiple "workflows" - use git's commands to power a mercurial repository.
Add hooks/callbacks in minutes.