tches
additional (optional, doesn't change anything in situation when
either the library or the python feature is not available)
functionality using the library for the additional parsing of the
spec file.
Signed-off-by: Matěj Cepl
---
runtime/ftplugin/spec.vim | 29 +++
On 2013-10-01, 18:08 GMT, Bram Moolenaar wrote:
> Sounds good, but does this work for everybody? I would like to hear
> from users, both with and without Python. No weird error messages in
> some environment?
Well, I have covered all my code with
if has('python')
endif
so I hoped tha
This patches
additional (optional, doesn't change anything in situation when
either the library or the python feature is not available)
functionality using the library for the additional parsing of the
spec file.
Signed-off-by: Matěj Cepl
---
runtime/ftplugin/spec.vim | 30
From: Matěj Cepl
With the rising complexity of our spec files, I get more to the
situations when spec.vim is not able to parse the spec file
properly and doesn't generate verrel properly.
However, we have rpm-python library in Fedora/RHEL/SUSE, which should be
able to parse anything val
com/p/vim/issues/detail?id=76 ... it has been
rebased to cleanly apply on the current tip of vim repo).
Best,
Matěj Cepl
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.v
From: Jan Synáček
Currently the spec highlighting doesn't recognize '_unitdir'
Fixes #76
---
runtime/syntax/spec.vim | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/runtime/syntax/spec.vim b/runtime/syntax/spec.vim
index 5d96b57..e94d62e 100644
--- a/runtime/syntax/spec.vim
On 2014-09-23, 19:25 GMT, Bram Moolenaar wrote:
> Have you tried contacting the maintainer, Igor Gnatenko?
Ouch ... I have completely missed that the file has
a maintainer. I am sorry, Igor. What do you think about my
attempt? (Whole thread is available at
http://thread.gmane.org/gmane.editors.
On 2016-08-07, 11:27 GMT, manuelschiller.pimail via vim_dev wrote:
> Please let me know if it would be possible to include this,
> and if not, at least the patch is public now where people can
> find it if they want it.
https://github.com/vim/vim/issues/418#issuecomment-246748135
and the (comple
On 2016-08-08, 12:50 GMT, Tony Mechelynck wrote:
> You should see, in that order, the glyphs for ff fi fl ft st
> ffi ffl.
> I absolutely don't like them (in the monospaced fonts that
> have them; in serif or sans-serif fonts it's different,
> especially in serif italic). OTOH, I think that expa
On 2016-08-11, 15:40 GMT, Kazunobu Kuriyama wrote:
>> Screenshot attached. (I haven't try PragmataPro.)
>
> I don't either for an obvious reason..Isn't there a free version? :)
Would https://github.com/tonsky/FiraCode/ work?
Matěj
--
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG
On 2016-09-14, 13:28 GMT, manuelschiller.pimail via vim_dev wrote:
> It allows users to hand-tune for which characters they want to
> bypass the glyph cache by putting a line in .vimrc, e.g.
>
> let g:gtk_nocache=[0x, 0xfc00, 0xf801, 0x7801]
>
> This contains a bitmap for each
On 2016-09-14, 13:28 GMT, manuelschiller.pimail via vim_dev wrote:
> It allows users to hand-tune for which characters they want to
> bypass the glyph cache by putting a line in .vimrc, e.g.
>
> let g:gtk_nocache=[0x, 0xfc00, 0xf801, 0x7801]
Tell me, please, you have never eve
I have built vim 8.0.003 on RHEL-7 with Gtk3
(gtk3-3.14.13-20.el7.x86_64) and everything works nice (thank
you!) except I get plenty of warnings on stderr:
(gvim:10610): Gtk-WARNING **: GtkNotebook 0x28001e0 is mapped
but visible child GtkEventBox 0x2802150 is not mapped
According to my colleag
On 2016-09-15, 12:33 GMT, manuelschiller.pimail via vim_dev wrote:
> Hi Matěj, Christian,
>
> I've added the value which is equivalent to the previous patch, i.e.
>
> " this should keep character 0-31 (control characters), and
> " [0-9A-Za-z] flowing through the glyph cache, and the rest
> " < 12
On 2016-09-15, 14:52 GMT, manuelschiller.pimail via vim_dev wrote:
> Well, I was thinking along the lines that using these special
> ligature glyphs is definitely a matter of preference. (For
> example, Bram had a pretty strong opinion about ">=/<=" and
> how he would not like to see ligatures f
On 2016-09-15, 16:42 GMT, Matěj Cepl wrote:
> That’s probably a good point: looking at issues on
> https://github.com/tonsky/FiraCode/issues and
> https://github.com/tonsky/FiraCode/wiki it seems there is
> truly not The Right Way™ how to do it (especially, if Haskell
> peop
On 2016-09-20, 01:15 GMT, Gary Johnson wrote:
> I tried to send email to the maintainer, Raul Segura Acevedo,
> but it was returned because the recipient address was rejected
> by the remote host.
>
> Would someone like to take over maintainership of that file
> and fix this? I can fix it, but
On 2016-10-16, 07:29 GMT, Rick Woo wrote:
>> I personally don't think it is worthwile to have yet another
>> language embedded into Vim.
>
> Then why put lua, perl, python 2 and 3 and tcl in Vim.
> Why phper can't have right or fun like them???
I agree … we should get rid of TCL, Lua, and Perl su
On 2016-10-26, 17:26 GMT, Charles E Campbell wrote:
> If you're using utf-8, its easy to get the glyph transform
> with mathmenu.vim (comes with
> http://www.drchip.org/astronaut/vim/index.html#MATH): type >=, select
> with visual-block (ctrl-v), then press the "&" key. Same sort of thing
> for
On 2016-10-26, 22:23 GMT, Tony Mechelynck wrote:
> Don't make the too frequent error to believe that everyone
> else, or at least most of them, has the same preferences as
> you. The fact that we hardly ever see a post about whether or
> not vimballs are the way to go does not necessarily mean t
On 2016-10-27, 11:58 GMT, Tony Mechelynck wrote:
> Ohhh, so that's what you mean. Well, here is another try: Not
> being imitated, or not being a copycat himself, don't
> necessarily mean that Dr. Chip is wrong, especially with Vim,
> which prides himself about allowing the users to obtain the
On 2016-10-27, 21:01 GMT, Charles E Campbell wrote:
> Well, I don't intend to spend hours re-inventing my scripts
> which do a lot of housekeeping and are responsible for
> updating my website, and which work with vimballs. Nor am
> I about to start keeping your and other's git repositories
>
On 2017-02-13, 23:41 GMT, Bram Moolenaar wrote:
> I think what you are seeing here is intentional. When you
> type exactly the characters that fit, Vim won't scroll the
> display up until you type another character. It's not really
> a problem, right?
I am not sure whether it is the same, but
Hi,
would it be possible to do something about display of the soft
hyphen character (U+00AD)? I tried to use it in my rST file, but
ended up with a blank space. So I filed a bug against the font
I use (https://github.com/tonsky/FiraCode/issues/365), but
maintainer of the font (unfortunately co
On 2017-02-17, 10:14 GMT, Matěj Cepl wrote:
> would it be possible to do something about display of the soft
> hyphen character (U+00AD)? I tried to use it in my rST file,
> but ended up with a blank space. So I filed a bug against the
> font I use (https://github.com/tonsky/FiraCod
On 2017-02-17, 10:29 GMT, Dominique Pellé wrote:
> See :help 'listchars' and the section about nbsp there.
> You need a Vim version recent enough, but nbsp has
> been added a long time ago.
I am not talking about (U+00A0), but about soft hyphen
(U+00AD), which is not covered by listchars.
On 2017-02-17, 12:15 GMT, Christian Brabandt wrote:
>:call matchadd('Conceal', '\%uad', 10, -1, {'conceal': '_'})
>:setl concealcursor=nv conceallevel=2
This is actually pretty good. Only it would be useful if we
could say to the spellchecker to ignore this character, so the
word wouldn’t be div
On 2017-02-17, 13:31 GMT, Matěj Cepl wrote:
> On 2017-02-17, 12:15 GMT, Christian Brabandt wrote:
>>:call matchadd('Conceal', '\%uad', 10, -1, {'conceal': '_'})
>>:setl concealcursor=nv conceallevel=2
>
> This is actually pretty good. O
On 2017-09-09, 20:20 GMT, Bram Moolenaar wrote:
> Patch 8.0.1085
> Problem:The terminal debugger can't set breakpoints.
> Solution: Add :Break and :Delete commands. Also commands for stepping
> through code.
> Files: runtime/pack/dist/opt/termdebug/plugin/termdebug.vim,
>
On 2017-09-24, 11:18 GMT, Gaspar Chilingarov wrote:
> If you have a need of RPM package - let me know in issues and
> I'll try automating it as well.
If you have need for RPM package (and you are on RHEL or Fedora)
you can use my packages at
https://copr.fedorainfracloud.org/coprs/mcepl/vim8/
On 2017-11-02, 05:40 GMT, Dominique Pellé wrote:
> I see that the neovim github page has a
> debian CI badge. See:
> https://github.com/neovim/neovim
That seems like pretty silly thing to do (speaking me as user of
Fedora/RHEL). Should vim carry some kind of badges for all (how
many it is?) dist
On 2017-11-02, 11:16 GMT, Dominique Pellé wrote:
> I don't think it's silly. It helps to find bugs in Vim on
> platforms that are rarely used. I was not aware of vim crashes
> on alpha or hurd x86 until I saw those debian test logs of
> vim-8.0.1241. If someone has the time they could be
> inv
On 2017-11-02, 11:16 GMT, Dominique Pellé wrote:
> For Fedora, I see this link:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=992971
> ... but it only seems to have compilation logs, not test logs
> which it less useful than the debian page.
I can also do build on the internal systems (I
On 2017-11-02, 11:16 GMT, Dominique Pellé wrote:
> For Fedora, I see this link:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=992971
> … but it only seems to have compilation logs, not test logs
> which it less useful than the debian page.
Testsuite is not run while building Fedora/RHEL
On 2017-11-04, 16:02 GMT, K.Takata wrote:
> I also use editorconfig-vim, and I *personally* think it is
> useful. However, the most important thing is that we need
> explicit permission from the author.
My problem is that it covers too narrow set of variables (for
example I would love to have a
On 2017-11-04, 19:43 GMT, Bram Moolenaar wrote:
> - It requires Python. It appears just because an existing
> parser existed in Python. Using an external Python program
> seems clumsy and slow.
I have strictly no position on whole idea, but just let me tell
that there are zillions of pars
On 2017-12-14, 14:01 GMT, chdiza wrote:
> When I try, …
Absolutely no flamebait intended, but why in the world would
anybody do it? It is not more lightweight (because you have to
run XServer), it is ugly as hell, and completely disjoint from
the platform UI.
Really only curious about the effo
On 2017-12-15, 22:08 GMT, Matěj Cepl wrote:
> yes, ``set mouse=a`` in ``~/.vim/vimrc`` did the trick. It
> might be helpful to add mention of it in the Termdebug help,
> because it could be the only place in the terminal vim where
> mouse is used.
Or perhaps the ``:Termdebug`` c
On 2018-02-03, 00:35 GMT, Ni Va wrote:
> Then just wonder why vimball is integrated within vim distro
> and not others plugin's managers like vimplug
> : https://github.com/junegunn/vim-plug.git
https://shapeshed.com/vim-packages/
(put your ~/.vim in a git repo, then those plugins could be git
On 2018-02-03, 14:56 GMT, Bram Moolenaar wrote:
> + \ 'python': [['#!/path/python']],
What about /usr/bin/python2 and /usr/bin/python3
> + \ 'javascript': [['#!/path/node'],
> + \['#!/path/nodejs'],
> + \['#!/path/rhino']],
/usr/bin/js and
On 2018-02-03, 21:35 GMT, Bram Moolenaar wrote:
> I notice that "js" is another name for nodejs. I don't see
> "js{version}", would one use that in a script shebang line?
Probably not. I admit these scripts are quite rare
(surprisingly), but I guess it can be alias to
$DEFAULT_JS_INTEPRETER qui
On 2018-02-27, 22:08 GMT, Tony Mechelynck wrote:
> The plugin is published in Vimball format.
And also available on https://github.com/chrisbra/unicode.vim
Best,
Matěj
--
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
Do
On 2018-02-28, 11:59 GMT, Christian Brabandt wrote:
> BTW: there is still an issue open that requests distributing
> the plugin with Vim. That would be Brams decision however.
Doesn’t patch 1553 make your plugin at least partially
redundant?
Matěj
--
https://matej.ceplovi.cz/blog/, Jabber: mc.
43 matches
Mail list logo