On Sunday, 29 Mar 2020 at 01:18, Adam Porter wrote:
> Pressing TAB (or any other key that moves to the next field) to realign
> a table is not a significant burden. A feature like this should
> probably remain an add-on package, or at least disabled by default.
I tend to work with large tables an
> I suggest being very careful with this. While it's a very nice feature,
> it's bound to be slow with large tables. And it is very frustrating for
> users when typing becomes laggy.
The feature could be an optional minor mode first and then later made
default if it proves to work well in every
ndame writes:
> As for org-at-table-p being slow storing the start and end position of
> the table could be a solution, so if point is between them then there
> is no need to check org-at-table-p again.
>
> org-table-align seemed fast enough for me when I tried the posted
> code, but if it's slow
> The idea is nice, and probably a step in the right direction, but
> `org-at-table-p' and `org-table-align' are not lightweight functions. In
> some common situations, e.g., when the table is a bit large, or when it
> is located away from the start of a section, typing in the table may
> feel slug
Hello,
ndame writes:
> The other day a code was posted on Reddit which automatically formats
> the table as you type:
>
> https://i.imgur.com/lorIDhY.gif
>
>
> The code looks pretty simple, the actual formatting code is only a few lines
> and it might even be possible to rewrite it to simplify i
The other day a code was posted on Reddit which automatically formats
the table as you type:
https://i.imgur.com/lorIDhY.gif
The code looks pretty simple, the actual formatting code is only a few lines
and it might even be possible to rewrite it to simplify it even more:
https://reddit.com/r/e
