This would be easier if we actually had a solid 'new design'. We don't.
We just have a bunch of rough ideas. One of those ideas had a drafted
structure and suggestion that it be used only in the input queue, where
the memory inefficiency would not be a concern. I have pointed out that
there
That said, I think there is a compromise. Vim has features, maybe the
new input mechanism could simply be a feature, something like
+enhanced_term_input (like we have for +python or +eval), and plugins
could simply check with stuffs like:
With an option like :set
So basically backward compatibility and memory efficiency are what
hold vim back in 1970. You made a lot of good points and reasons for
it to be so, but I'm always sad when good ideas are refused just
because of old scenarios.
I don't think anybody has refused the idea, and I don't think
This is my first time joining a discussion, I had a hard time just to
open an account and send my suggestion. I use the default reply
function and I don't mean to upset anyone. Hopefull now this reply is
well-edited (I removed the quote).
Yes, it was a much better reply, thanks, Stephen. And
Patch 7.3.127
Problem:Compiler complains about comma.
Solution: Remove comma after last enum element.
Files: src/ex_cmds2.c
*** ../vim-7.3.126/src/ex_cmds2.c 2010-12-17 18:06:00.0 +0100
--- src/ex_cmds2.c 2010-12-17 19:58:37.0 +0100
***
***
Patch 7.3.130
Problem:Variable misplaced in #ifdef.
Solution: Move clipboard_event_time outside of #ifdef.
Files: src/gui_gtk_x11.c
*** ../vim-7.3.129/src/gui_gtk_x11.c2010-08-15 21:57:31.0 +0200
--- src/gui_gtk_x11.c 2010-12-04 15:26:41.0 +0100
***
Patch 7.3.131
Problem:Including errno.h too often.
Solution: Don't include errno.h in Unix header file.
Files: src/os_unix.h
*** ../vim-7.3.130/src/os_unix.h2010-08-15 21:57:28.0 +0200
--- src/os_unix.h 2010-12-17 20:05:34.0 +0100
***
***
Patch 7.3.132
Problem:C++ style comments.
Solution: Change to C comments.
Files: src/if_python3.c
*** ../vim-7.3.131/src/if_python3.c 2010-11-16 19:25:56.0 +0100
--- src/if_python3.c2011-01-16 01:28:35.0 +0100
***
*** 22,29
* Adaptations to
Patch 7.3.128
Problem:Another compiler warning for signed pointer.
Solution: Use unsigned int argument for sscanf().
Files: src/mark.c
*** ../vim-7.3.127/src/mark.c 2010-08-15 21:57:25.0 +0200
--- src/mark.c 2010-12-17 20:00:05.0 +0100
***
*** 1750,1756
Patch 7.3.129
Problem:Using integer like a boolean.
Solution: Nicer check for integer being non-zero.
Files: src/tag.c
*** ../vim-7.3.128/src/tag.c2010-12-17 18:06:00.0 +0100
--- src/tag.c 2010-12-17 17:49:35.0 +0100
***
*** 204,210
else
Patch 7.3.133
Problem:When using encryption it's not clear what method was used.
Solution: In the file message show blowfish when using blowfish.
Files: src/fileio.c
*** ../vim-7.3.132/src/fileio.c 2011-02-15 17:39:14.0 +0100
--- src/fileio.c2011-02-25
This is my first time joining a discussion, I had a hard time just to
open an account and send my suggestion. I use the default reply
function and I don't mean to upset anyone. Hopefull now this reply is
well-edited (I removed the quote).
About vim, I misunderstood that it was a keyboard
Lilydjwg wrote:
I made a patch to fix some bugs related to Vim's Python3 support. The
bugs I found are:
* vim.error is a `str` instead of an `Exception` object, so `except` or
`raise` it causes a `SystemError` exception
* buffer objects do not support slice assignment
* when exchange
Patch 7.3.126
Problem:Compiler warning for signed pointer.
Solution: Use unsigned int argument for sscanf().
Files: src/blowfish.c
*** ../vim-7.3.125/src/blowfish.c 2010-08-15 21:57:28.0 +0200
--- src/blowfish.c 2010-12-17 19:58:18.0 +0100
***
Hi,
I use a shared additional vim spell file that contains word marked as bad
like 'foo/!'. For words that can be written in different correct ways, which
at least exists in German, sometimes one of both variants is marked as bad
to help writing uniform texts. To distinguish these explicit bad
Patch 7.3.135
Problem:When there is no previous substitute pattern, the previous search
pattern is used. The other way around doesn't work.
Solution: When there is no previous search pattern, use the previous
substitute pattern if possible. (Christian Brabandt)
Another way to extend this might be to switch from a byte queue to a short
integer
queue. The lower 8-bits would be as it is now; the upper eight bits would encode
modifier keys (shift, ctrl, alt, meta, whatever).
I think sticking to the byte queue is best. So much in Vim relies on
text being
17 matches
Mail list logo
