zk-phi / cedit Goto Github PK

Test code:

public function test()
{
    $bundles = array(
        'test test test test test test test test',
        'foo bar foo bar foo bar foo bar foo bar',
        'foo bar baz quux foo bar baz quux',
    );
}

With point at |$bundles, cedit-end-of-statement throws an error "not found (59 125)".
With point at )|;, cedit-beginning-of-statement throws an error "Lisp nesting exceeds `max-lisp-eval-depth'"

The error doesn't happen with the code below; both functions work as expected.

public function test()
{
    $bundles = array(
        'test test test test test test test',
        'bar foo bar foo bar foo bar foo bar',
        'bar baz quux foo bar baz quux',
    );
}

It's the same whether the array is full of strings or function calls.

I currently bind cedit-foward/backward-char to C-f and C-b. However, when using the functions on an open parenthesis, it just skips to the closing parenthesis. There's no way to go into the pair with cedit function; cedit-down-block considers anything other than { } is not a block and does nothing.

cedit-down-block should be applicable to pairs such as ( ) and [ ], similar to how paredit does. Otherwise, cedit-forward/backward-char should just move the cursor normally over those characters.

The attributes cause Readme.org to be always dirty:

$ git status
# On branch master
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#       modified:   Readme.org
#
no changes added to commit (use "git add" and/or "git commit -a")
$ git checkout -- Readme.org
$ git status
# On branch master
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#       modified:   Readme.org
#
no changes added to commit (use "git add" and/or "git commit -a")

To me it looks like this file were put in place by some tool you were using to initialize the repositories and there is not real reason why .gitattributes would have exist. If that is so please remove them. Otherwise please fix them so that files are not marked as modified when they are not. .gitignore also does not appear to include any relevant rules, but at least it's not causing any harm.

indent-guide, scratch-palette, and probably others have the same problem.