Every one of the projects in this repository is available at the canonical
URL git://git.madduck.net/madduck/pub/<projectpath> — see
each project's metadata for the exact URL.
All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@git.madduck.net.
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
Daniel Hahler [Wed, 6 May 2015 13:12:26 +0000 (15:12 +0200)]
Improve handling of lookup in previous lines
- Handle jedi-vim call signatures when looking for colon and function
def in previous line.
This adds `jedi\S` to s:skip_special_chars and improves the algorithm to
find the colon in the previous line in `s:indent_like_previous_line`.
- Add `s:match_expr_on_line` and use it for `nothing_after_opening_paren`.
- Handle comments after opening paren (#32).
NOTE: This handles older Vim versions, where `synconcealed` behaves different
(returns an empty list for non-concealed) and `getcurpos` is not
available (Vim 7.3.429 (used on Travis)).
Hassan Kibirige [Thu, 13 Mar 2014 09:50:20 +0000 (04:50 -0500)]
Refix issue #5 (Correct indent after end of block)
The implementation clean up reintroduced a more severe
version of the bug. Plus, the test was slightly deficient
to catch the regression.
Problem
-------
Given two adjacent blocks where the 2nd block has
an equal or smaller indentation level compared to the 1st
block. If the 1st block does not end in a stop statement
it always sucks up the 2nd block.
This changes the meaning of code that already adheres to the
pep8 standard.
Solution
--------
Do not inherit indentation of the previous line if the current line
has less indentation but is valid.
has2k1 [Thu, 31 Oct 2013 10:17:16 +0000 (05:17 -0500)]
Fix issue #5 (Correct indent after end of block)
Problem
-------
Given two adjacent blocks where the 2nd block has
an equal or smaller indentation level compared to the 1st
block. If the blocks are not separated by an empty line,
the 2nd block will be placed (indented) inside the 1st
block.
This changes the meaning of code that already adheres to the
pep8 standard.
Solution
--------
Do not inherit indentation of the previous line if the current line
has less indentation but is valid.
Reason
------
The indent functions, in this case
GetPythonPEPIndent()
can modify the cursor position. There is nothing wrong with that
consequence, vim takes it into account and restores the cursor
position (see References below). For the tests vim is not doing
the calling, so the cursor is not restored.
Solution
--------
Restore the cursor position after calling the indent function.
Joseph Irwin [Sat, 18 Aug 2012 04:18:25 +0000 (13:18 +0900)]
Do not indent after comment line with colon
When checking for a line ending with a colon, this commit adds a
condition to avoid matching comments. A comment line ending with a colon
should not indent a new block.
projects / etc / vim.git / log