| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
I think it should be `,,c` for creation, `,,f` for reformatting, correct?
|
|\
| |
| | |
Add check to be able to create a top page table
|
|/
|
|
|
| |
This commit adds a check for top boundary, so if the table
goes up to the top of the document, it will be correctly detected.
|
|\
| |
| | |
when modifying a table maintain its current indentation
|
|/
|
|
| |
this allows vim-rst-tables to be used inside an outliner like the vim votl plugin
|
|\
| |
| | |
Fix rendering of README. Thanks, @erisian!
|
|/
|
|
| |
GitHub's renderer.
|
|\
| |
| | |
Support tables containing East Asian languages, too.
|
|/
|
|
| |
calculate string length as unicode type, not str type
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Apparently, RST requires the first line of tables to be drawn with
minuses, not equal signs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example, if you have the following table in your source file:
Type Message
Foo I like bananas very much. Even so much that I adore them.
Position your cursor in it and call ReformatTable(). This makes the
following:
+======+===========================================================+
| Type | Message |
+======+===========================================================+
| Foo | I like bananas very much. Even so much that I adore them. |
+------+-----------------------------------------------------------+
But if you don't like these kinds of long wrappings, you can now simply
remove (or add, for that matter) some of the '='-signs from the top row,
like this:
+======+================================+
| Type | Message |
+======+===========================================================+
| Foo | I like bananas very much. Even so much that I adore them. |
+------+-----------------------------------------------------------+
And then, call ReflowTable():
+======+================================+
| Type | Message |
+======+================================+
| Foo | I like bananas very much. Even |
| | so much that I adore them. |
+------+--------------------------------+
This fixed issue #1.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example, when given the following table:
[['Foo', 'Bar'],
['x', 'This is a long line\nthat is spread out\nover multiple lines']]
It will render as:
+=====+=====================+
| Foo | Bar |
+=====+=====================+
| x | This is a long line |
| | that is spread out |
| | over multiple lines |
+-----+---------------------+
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Is able to parse tables of the form:
+=====+=====================+
| Foo | Bar |
+=====+=====================+
| x | This is a long line |
| | that is spread out |
| | over multiple lines |
+-----+---------------------+
Into:
[['Foo', 'Bar'], ['x', 'This is a long line\nthat is spread out\nover multiple lines']]
The draw_table function needs to be written still, though.
|
|
|
|
| |
This implementation only needs ReformatTable(), also for creation.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|