Re: Patch 8.0.1553
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...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 He can compress the most words into the smallest idea of any man I know. -- Abraham Lincoln -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1553
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 not pity the dead, Harry. Pity the living, and above all, the people who watched [Harry Potter and the Cursed Child]. -- Philami on https://is.gd/f9VMaC -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1458
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 quite easily, so it is probably The Right
Thing™ to check for.
Best,
Matěj
--
http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
"Push to test." (click) "Release to detonate..."
-- from a bugzilla quip list
--
--
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.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1458
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 /usr/bin/js{version} ? (We have Mozilla's
Spidermonkey packaged as such in Fedora/RHEL, but I guess it is
available for other Linuces as well, I see it as libmozjs-*-bin
packages on Debian as well)
Best,
Matěj
--
http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
Afraid to die alone?
Become a bus driver.
-- alleged easter egg in notepad++
--
--
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.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: vimball, vundle vimplug compatibility
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 submodules). Best, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Ludwig Boltzmann, who spent much of his life studying statistical mechanics, died in 1906, by his own hand. Paul Ehrenfest, carrying on the work, died similarly in 1933. Now it is our turn to study statistical mechanics. -- David L. Goodstein “States of Matter” -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [vim/vim] Termdebug buttons don't work in gnome-terminal (#2452)
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`` command could set ``mouse=a``? Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Roses are red; Violets are blue. I'm schizophrenic, And so am I. -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [vim/vim] Vim can't build the athena GUI on macOS High Sierra (#2444)
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 effort. Thanks for any reply, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Whittaker Chambers said the particular temptation of the modern world is to think that “the destiny of man is in the hands of man.” Those who think so, he said, would end up committing greater and greater evils in the name of saving humanity. -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [vim/vim] Proposal: ship with EditorConfig plugin by default (#2286)
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 parsers of EditorConfig files (https://github.com/editorconfig/) including C (https://github.com/editorconfig/editorconfig-core-c). I don’t think there is a parser written in VimL. Best, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 The difference between death and taxes is death doesn't get worse every time Congress meets -- Will Rogers -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [vim/vim] Proposal: ship with EditorConfig plugin by default (#2286)
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 an equivalent of 'spell' and 'spelllang' for my rST editing). Best, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 He can compress the most words into the smallest idea of any man I know. -- Abraham Lincoln -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [patch] added debian build badge
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 packages apparently. I have run vim8-1245 locally on RHEL_7/x86_64 and the logs are https://mcepl.fedorapeople.org/tmp/vim-1245-check-logs.zip Also, I run the same src.rpm package here https://copr.fedorainfracloud.org/coprs/build/657132/ Best, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 It is the mark of an educated mind to be able to entertain a thought without accepting it. -- Aristotle -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [patch] added debian build badge
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 have easily ppc, x86_64, s390, aarch64, ppc64le, ppc64, i686, and s390x available), unfortunately they are not available from outside. I can put logs somewhere. Best, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 He loves nature in spite of what it did to him. -- Forrest Tucker -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [patch] added debian build badge
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 > investigated. We should be able to run hurd with QEMU for > example. For that you should have maintainers on these platforms, centralization in one place doesn’t scale. Karsten Hopp just have been doing too fine job of maintaining vim on Fedora/RHEL to be ignored. > 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. Yeah, we don’t seem to run make check during the build, all testing would be in that one log if we did. How to run a testsuite? Do you need to do something with ./configure or it just running ``make check``? I can switch that on in my COPR on https://copr.fedorainfracloud.org/coprs/mcepl/vim8/ Best, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 If you have a problem and you think awk(1) is the solution, then you have two problems. -- David Tilbrook (at least 1989, source of the later famous jwz rant on regular expressions). -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [patch] added debian build badge
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?) distros and operating systems it works on? Best, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 According to the Franciscan priest Richard Rohr, spirituality is not for people who are trying to avoid hell; it is for people who have been through hell. In many ways, spirituality is about what we do with our pain. And the truth is, if we don't transform it, we will transmit it. -- Al Gustafson -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [vim/vim] Rendering issues with ligatures (#418)
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/ Best, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 A philosopher like Plato, according to Luther's colorful imagery, remains like a cow who looks at a new door, refusing to enter? -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1085
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, > runtime/doc/terminal.txt Is there some way how to make termdebug working with other debugger (I would be interested in pdb, of course)? That would be really awesome! The only thing which makes me thing about VSCode or PyCharm is missing debugger in vim (and all plugins I found are more or less broken). Best, Matěj -- http://matej.ceplovi.cz/blog/, Jabber: mceplceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Q: What is the chief end of man? A: The chief end of man is to glorify God and to enjoy him forever. -- The Westminster Shorter Catechism -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: RFE: Add (U+00AD) to listchars
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. Only it would be useful if we
> could say to the spellchecker to ignore this character, so the
> word wouldn’t be divided for purposes of spell checking.
Hmm, I see a problem. Unfortunately this makes all highlights
hidden and replaced with _ including highlighted searches. Any
thoughts?
Matěj
--
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
England is governed not by logic but by parliament.
-- Benjamin Disraeli
--
--
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.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: RFE: Add (U+00AD) to 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 divided for purposes of spell checking.
Anyway, thank you.
Matěj
--
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
My life has been full of terrible misfortunes most of which never
happened.
-- Michel de Montaigne
--
--
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.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: RFE: Add (U+00AD) to listchars
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. And that’s exactly RFE I have. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 "Push to test." (click) "Release to detonate..." -- from a bugzilla quip list -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: RFE: Add (U+00AD) to listchars
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/FiraCode/issues/365), > but maintainer of the font (unfortunately correctly, IMO) > closed it as NOTABUG. > > I think adding new item 'shy' to the possible keys of listchars > variable should be a good solution, what do you think? And, BTW, Emacs (emacs-25.1-3.fc25.x86_64) using the same font does The Right Thing™ displaying the hyphen character in different color. Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 In the government of this Commonwealth, the legislative department shall never exercise the executive and judicial powers, or either of them: The executive shall never exercise the legislative and judicial powers, or either of them: The judicial shall never exercise the legislative and executive powers, or either of them: to the end it may be a government of laws and not of men. -- John Adams in the Article XXXth of the Constitution of the Commonwealth of Massachusetts -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RFE: Add (U+00AD) to listchars
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 correctly, IMO) closed it as NOTABUG. I think adding new item 'shy' to the possible keys of listchars variable should be a good solution, what do you think? Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 This is a signature anti-virus. Please stop the spread of signature viruses! -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [vim/vim] The scroll does not keep up the cursor on some situation. (#1474)
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 I have here with 8.0-324 and Gtk3 GUI repeated problems with vim skipping letters when writing a longer text (ft=rst). When I write a longer sentence, sometimes only few letters remain in the buffer. Is it a known problem? Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 He can compress the most words into the smallest idea of any man I know. -- Abraham Lincoln -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 > up-to-date. That said, I don't mind your git repositories, > its just that I won't be using them. I haven’t expected you to do either of these. > Bram asked me to come up with a vim-based way years ago to > handle vim plugins; that is the provenance of vimball. Prior > to that I myself used tar and gzip. Right, 818 lines of unused vim code is probably more than I would like to have, but it is not that bad (I was afraid, that some parts of vimballs require C implementation, so that it is part of vim C codebase). On the other hand, I am not sure why vimball should not be kept in a separate external project as all other package managers do, but it is probably not that big deal. Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 I would like to die sleeping, like my father — rather than screaming and helpless, like his passengers. -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 > same results by different means. I don't even know whether Dr. Chip was wrong when he invented vimballs. His crystal ball was obviously a bit murky so he haven’t expected git (and particularly GitHub) typhoon. Either because of that or for whatever other reason vimballs really are not that widespread as was expected when they became part of vim. I believe it is time to accept the reality and move on. Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Never ascribe to malice that which is adequately explained by stupidity. -- Napoleon Bonaparte (or many other people to whom this quote is ascribed) -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 that > everyone dislikes them the way you do. On the contrary, > I would intrpret that silence as meaning that the current > state of affairs is OK for most people, because if it weren't > they would complain. I hardly ever see such a complaint, yours > is a "once in a blue moon" thing. I don’t think this is the case. I have been following a lot of vim-related news and communications in the last year or more, and I have found a lot of plugins which are just uploaded to vim.org/scripts/ (mostly tarballs or zip archives), and a lot of plugins which are in a git repo (99.9% cases in GitHub). This is the first vimball I see in a long long time. And you are wrong if you except complains ... featuretitis doesn’t represent itself by complaints from users. Only by the rotting code, and emerging (security and other) bugs. Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 The state is the great fictitious entity by which everyone seeks to live at the expense of everyone else. -- Frederick Bastiat -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 <=, too. > Lower case: select letter(s), press "_". Upper case: select letter(s), > press "^". Etc. Thank you very much. However, I have to say it. My first step was to create a git repo https://gitlab.com/mcepl/math-vba and use it via preferred pathogen-style package manager of my choice (vim-plug in my case). I know that vimballs are you baby, but isn't the time to admit defeat and give up on it and declare pathogen-style repos as a preferred way of dealing with vim plugins? It was an interesting idea, but it just didn't catch with the vim population it seems. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 The state is the great fictitious entity by which everyone seeks to live at the expense of everyone else. -- Frederick Bastiat -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [vim/vim] Is it possible that vim support php like Python? (#1172)
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 support in vim. In reality I see plugins either in plain VimL, or (when more serious programming language is needed) in Python (py2 and py3 is just temporary problem given the situation in the Python world, in few years py2k will be finally gone). Did anybody see any Perl, Lua, or TCL vim plugin lately? Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 If the Good Lord had wanted us to enjoy ourselves, he wouldn’t have granted us His precious gift of relentless misery. -- Jean Calvin in "Calvin and the Chipmunks" comic strip https://mcepl.fedorapeople.org/tmp/calvin_and_the_chipmunks.jpg -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: NUL in syntax/cdl.vim
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 I don't use CDL, so > I wouldn't be an appropriate maintainer. It is git now, so nothing stops from adding a link to your pull suggesting a fix for the issue. Something like https://github.com/vim/vim/pull/1103 ? Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 As a rule of thumb, the more qualifiers there are before the name of a country, the more corrupt the rulers. A country called The Socialist People's Democratic Republic of X is probably the last place in the world you'd want to live. -- Paul Graham discussing (not only) Nigerian spam (http://www.paulgraham.com/spam.html) -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 > people get involved, who seem to have really weird > requirements; well, Haskell people ... enough said ;)). > However, I still hold that this variable should be seen by as > few people as possible. So, some sensible default should be > provided, and only weird people (like Bram ;)) should be sent > to detailed instructions how to fix it (or wiki pages, or > something). Actually, it might be interesting to find out “default ligatures” and “all ligatures” mean in https://github.com/robertvojta/LigatureXcodePlugin. I guess, they are trying to solve the same problem. Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use a hammer. -- IBM maintenance manual, 1925 -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 for these combinations, > I seem to remember.) 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 people get involved, who seem to have really weird requirements; well, Haskell people ... enough said ;)). However, I still hold that this variable should be seen by as few people as possible. So, some sensible default should be provided, and only weird people (like Bram ;)) should be sent to detailed instructions how to fix it (or wiki pages, or something). > I thought that not setting any option in .vimrc will produce > usable output (without ligatures) which is fine for the > majority of people who don't care about ligatures. No choice > involved for the unsuspecting user, it'll just work, and > produce unsurprising output for a hassle-free editing session > (albeit without the ligature eye-candy... ;). If you want to have this switched off, then I would prefer some ``ligatures_on`` Boolean preferences or something of that kind which would be easy to use. I would even argue that default off is a questionable choice, because if somebody installs Fira Code, I assume, she wants ligatures, why she would install this weird font otherwise (I would call it “The Principle of the Least Atonishment”, but somebody else used it)? But whatever, adults don’t argue about defaults, so whichever way it is, I can switch it on in ~/.vimrc myself. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 If in desperation, read the documentation! -- Brian D. Ripley, on R-help list -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 > " < 128 will bypass it > let g:gtk_nocache=[0x, 0xfc00, 0xf801, 0x7801] I had to make some typo or something, because when copying this line into my ~/.vimrc I got it working as before. Thank you! > About the criticism that this is not the most user-friendly > option to set: That's a very valid point. My reasoning was > thus: That was not my problem. Read http://www.joelonsoftware.com/uibook/chapters/fog59.html # Every time you provide an option, you're asking the user # to make a decision. I would even say, “you force the user to make decision”. And he will be grumpy for that. You should apologize every time you force user to do anything else than why he started to use your program in the first place. Which is why I said, that if you need this during the development, then I don't care. However, if normal user ever sees it, she will get fits and she would be right. > - The "user-facing part" depends very much on what people > would like to have. “Nothing” is the only possible answer, I think. > That said, I'm very happy for suggestions (or patches), and > will try to have a draft ready soonish when suggestions do > trickle in. :) Thank you very much for your work, despite my criticism. Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Quod fuimus, estis; quod sumus, vos eritis. -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Gtk3 warning on stderr
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 colleagues more knowledgeable about Gtk internals: Usually it means that something is manipulating the visibility of children manually, or it's blocking some signal emission. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 When you're happy that cut and paste actually works I think it's a sign you've been using X-Windows for too long. -- from /. discussion on poor integration between KDE and GNOME -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 ever considered this variable to be anything more than a cludge during the development? Please, tell me you never planned to inflict this on users (yes, I know, vim users are not normal humans, but still)! Please. Could you also add value of the variable which would be equivalent of the previous patch, please? I really don’t know how to make it work as well as the previous one? Otherwise, vim with your new patch builds on RHEL-7 without problem http://koji.fedoraproject.org/koji/taskinfo?taskID=15633602 Thank you, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 It is a rare mind indeed that can render the hitherto non-existent blindingly obvious. The cry “I could have thought of that” is a very popular and misleading one, for the fact is that they didn’t, and a very significant and revealing fact it is too. -- Douglas Adams, Dirk Gently's Holistic Detective Agency -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 character < 128, which has the > corresponding bit set if the glyph cache is to be bypassed > (which in turn enables ligatures). The default is no > ligatures, unless people set something like above in their > .vimrc. With this slightly more sophisticated patch, people > have the option to enable/disable certain ligatures by routing > the corresponding characters through the cache (or not) > without recompiling, if they so prefer. So, for example how to make >= and <= be included so that they translate into (glyphs from :digraphs): =< ≤ 8804 >= ≥ 8805 Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 The first mistake in publick business, is the going into it. -- Benjamin Franklin -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 ..every Man has a Property in his own Person. This no Body has any Right to but himself. The Labour of his Body, and the Work of his Hands, we may say, are properly his. The great and chief end therefore, of Mens uniting into Commonwealths, and putting themselves under Government, is the Preservation of their Property. -- John Locke, "A Treatise Concerning Civil Government" -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 expanding them > to two or three character cells would be ugly the opposite > way. It could be the problem with your font. I use https://github.com/tonsky/FiraCode/ and it seems to work for me just fine. Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 May you come to the attention of those in authority. May you find what you are looking for. May you live in interesting times. -- claimed to be a Chinese proverb, but its origin is disputed first documented use Frederic R. Coudert, Proceedings of the Academy of Political Science, 1939 -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gvim and ASCII glyphs
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 (completely unofficial) build for RHEL/CentOS-7 is on http://koji.fedoraproject.org/koji/taskinfo?taskID=15617207 Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Quod fuimus, estis; quod sumus, vos eritis. -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[PATCH] Use rpm Python library for parsing version and release info.
From: Matěj Cepl mc...@redhat.com
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 valid in any SPEC file. 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 mc...@cepl.eu
---
runtime/ftplugin/spec.vim | 32 ++--
1 file changed, 30 insertions(+), 2 deletions(-)
diff --git a/runtime/ftplugin/spec.vim b/runtime/ftplugin/spec.vim
index c3af8a9..5f7d641 100644
--- a/runtime/ftplugin/spec.vim
+++ b/runtime/ftplugin/spec.vim
@@ -20,11 +20,36 @@ endif
noremap buffer unique script PlugSpecChangelog :call
SIDSpecChangelog()CR
+if !exists(*s:GetRelVer)
+function! s:GetRelVer()
+if has('python')
+python PYEND
+import sys, datetime, shutil, tempfile
+import vim
+
+try:
+import rpm
+except ImportError:
+pass
+else:
+specfile = vim.current.buffer.name
+if specfile:
+spec = rpm.spec(specfile)
+headers = spec.packages[0].header
+version = headers['Version']
+release = ..join(headers['Release'].split(.)[:-1])
+vim.command(let ver = + version)
+vim.command(let rel = + release)
+PYEND
+endif
+endfunction
+endif
+
if !exists(*s:SpecChangelog)
function s:SpecChangelog(format)
if strlen(a:format) == 0
if !exists(g:spec_chglog_format)
- let email = input(Email address: )
+ let email = input(Name email address: )
let g:spec_chglog_format = %a %b %d %Y .
l:email
echo \r
endif
@@ -69,6 +94,9 @@ if !exists(*s:SpecChangelog)
else
let include_release_info = 0
endif
+
+call s:GetRelVer()
+
if (chgline == -1)
let option = confirm(Can't find %changelog. Create
one? ,End of file\nHere\nCancel,3)
if (option == 1)
@@ -83,7 +111,7 @@ if !exists(*s:SpecChangelog)
endif
endif
if (chgline != -1)
- let parsed_format = * .strftime(format)
+ let parsed_format = * .strftime(format). -
.ver.-.rel
let release_info = + .name.-.ver.-.rel
let wrong_format = 0
let wrong_release = 0
--
1.8.3.1
--
--
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.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [PATCH] Use rpm Python library for parsing version and release info.
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? I know it is a little bit pervert to revive this almost two year old zombie, but let me try. So, what is missing from my patch fixing ftplugin/spec.vim (the first patch attached, also spec_vim branch of http://luther.ceplovi.cz/git/vim.git repository)? It fixes still unfixed issue https://code.google.com/p/vim/issues/detail?id=153 I have been using this plugin for more than year in my daily work and it seems to work just fine. I have also tested it with a build of vim without Python support and it worked the same as the original version of the plugin. Also, if you touch */spec.vim files you can apply patch of my colleague jsynacek (second attach, branch jsynacek in my repo, and fixing https://code.google.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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[PATCH] spec syntax: support %_unitdir in spec.vim
From: Jan Synáček jan.syna...@gmail.com 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 +++ b/runtime/syntax/spec.vim @@ -74,7 +74,7 @@ syn keyword specMacroNameOther contained buildroot buildsubdir distribution dist syn match specMacroNameOther contained '\\(PATCH\|SOURCE\)\d*\' valid _macro names from /usr/lib/rpm/macros -syn keyword specMacroNameLocal contained _arch _binary_payload _bindir _build _build_alias _build_cpu _builddir _build_os _buildshell _buildsubdir _build_vendor _bzip2bin _datadir _dbpath _dbpath_rebuild _defaultdocdir _docdir _excludedocs _exec_prefix _fixgroup _fixowner _fixperms _ftpport _ftpproxy _gpg_path _gzipbin _host _host_alias _host_cpu _host_os _host_vendor _httpport _httpproxy _includedir _infodir _install_langs _install_script_path _instchangelog _langpatt _lib _libdir _libexecdir _localstatedir _mandir _netsharedpath _oldincludedir _os _pgpbin _pgp_path _prefix _preScriptEnvironment _provides _rpmdir _rpmfilename _sbindir _sharedstatedir _signature _sourcedir _source_payload _specdir _srcrpmdir _sysconfdir _target _target_alias _target_cpu _target_os _target_platform _target_vendor _timecheck _tmppath _topdir _usr _usrsrc _var _vendor +syn keyword specMacroNameLocal contained _arch _binary_payload _bindir _build _build_alias _build_cpu _builddir _build_os _buildshell _buildsubdir _build_vendor _bzip2bin _datadir _dbpath _dbpath_rebuild _defaultdocdir _docdir _excludedocs _exec_prefix _fixgroup _fixowner _fixperms _ftpport _ftpproxy _gpg_path _gzipbin _host _host_alias _host_cpu _host_os _host_vendor _httpport _httpproxy _includedir _infodir _install_langs _install_script_path _instchangelog _langpatt _lib _libdir _libexecdir _localstatedir _mandir _netsharedpath _oldincludedir _os _pgpbin _pgp_path _prefix _preScriptEnvironment _provides _rpmdir _rpmfilename _sbindir _sharedstatedir _signature _sourcedir _source_payload _specdir _srcrpmdir _sysconfdir _target _target_alias _target_cpu _target_os _target_platform _target_vendor _timecheck _tmppath _topdir _usr _unitdir _usrsrc _var _vendor -- -- 1.8.3.1 -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [PATCH] Use rpm Python library for parsing version and release info.
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.vim.devel/42874/focus=47319) Thank you, Matěj -- -- 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.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_dev group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[PATCH] Use rpm Python library for parsing version and release info.
On 2013-10-02, 14:33 GMT, ZyX wrote:
1. Function s:GetRelVer does not give any error messages.
2. Yet it does nothing.
Not sure whether this behavior is fine.
It shouldn't matter. s:GetRelVer() is called on line 97, i.e.,
after ver and rel should be set as best as we can set it without
using the Python library. So, if s:GetRelVer() does nothing, no
harm is done and we are not worse than we would be without using
the Python library.
There is also a possible error:
+specfile = vim.current.buffer.name
+spec = rpm.spec(specfile)
. How rpm.spec() behaves if specfile is None? This is unlikely
because `None` means buffer with no file name (which means to
get this ftplugin loaded one needs to explicitly do `:set
filetype=spec` or `:filetype spec`) and not saved to disk, but
possible.
Good point! I have covered whole the rest of the Python function
with
if specfile:
...
(see the refreshed version of the patch below; still also
available at http://luther.ceplovi.cz/git/vim.git, branch
spec_vim)
Also from this patch I see that you are using `ver` and `rel`
in a function *different* from s:GetRelVer. But I do not see
you adding any assignments for `ver` and `rel`. In fact you
assign them in s:GetRelVer, but this function returns nothing.
Do you expect vim or python magically propagate these
variables to a separate scope? They will not. In fact new
function is not different from
They do, because s:GetRelVer() is called inside of
s:SpecChangelog() function so they are local to that function.
Notice, that I have been using this modification for almost
a year, so I happily accept any reasonable corrections, but trust
me, at least the basic functionality really works.
Also, I have very briefly tested this patch with vim built
without Python and I haven't noticed any problems. It works as
badly as it does without the Python library.
Bram, what do you think?
Matěj
=
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, which should be
able to parse anything valid in any SPEC file. 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 mc...@redhat.com
---
runtime/ftplugin/spec.vim | 30 +-
1 file changed, 29 insertions(+), 1 deletion(-)
diff --git a/runtime/ftplugin/spec.vim b/runtime/ftplugin/spec.vim
index 9778e1c..967da46 100644
--- a/runtime/ftplugin/spec.vim
+++ b/runtime/ftplugin/spec.vim
@@ -19,6 +19,31 @@ endif
noremap buffer unique script PlugSpecChangelog :call
SIDSpecChangelog()CR
+if !exists(*s:GetRelVer)
+function! s:GetRelVer()
+if has('python')
+python PYEND
+import sys, datetime, shutil, tempfile
+import vim
+
+try:
+import rpm
+except ImportError:
+pass
+else:
+specfile = vim.current.buffer.name
+if specfile:
+spec = rpm.spec(specfile)
+headers = spec.packages[0].header
+version = headers['Version']
+release = ..join(headers['Release'].split(.)[:-1])
+vim.command(let ver = + version)
+vim.command(let rel = + release)
+PYEND
+endif
+endfunction
+endif
+
if !exists(*s:SpecChangelog)
function s:SpecChangelog(format)
if strlen(a:format) == 0
@@ -68,6 +93,9 @@ if !exists(*s:SpecChangelog)
else
let include_release_info = 0
endif
+
+call s:GetRelVer()
+
if (chgline == -1)
let option = confirm(Can't find %changelog. Create
one? ,End of file\nHere\nCancel,3)
if (option == 1)
@@ -82,7 +110,7 @@ if !exists(*s:SpecChangelog)
endif
endif
if (chgline != -1)
- let parsed_format = * .strftime(format)
+ let parsed_format = * .strftime(format). -
.ver.-.rel
let release_info = + .name.-.ver.-.rel
let wrong_format = 0
let wrong_release = 0
--
1.8.4.474.g128a96c
--
--
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.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[PATCH] Use rpm Python library for parsing version and release info.
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, which should be
able to parse anything valid in any SPEC file. 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 mc...@redhat.com
---
runtime/ftplugin/spec.vim | 29 -
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/runtime/ftplugin/spec.vim b/runtime/ftplugin/spec.vim
index 9778e1c..e70bc71 100644
--- a/runtime/ftplugin/spec.vim
+++ b/runtime/ftplugin/spec.vim
@@ -19,6 +19,30 @@ endif
noremap buffer unique script PlugSpecChangelog :call
SIDSpecChangelog()CR
+if !exists(*s:GetRelVer)
+function! s:GetRelVer()
+if has('python')
+python PYEND
+import sys, datetime, shutil, tempfile
+import vim
+
+try:
+import rpm
+except ImportError:
+pass
+else:
+specfile = vim.current.buffer.name
+spec = rpm.spec(specfile)
+headers = spec.packages[0].header
+version = headers['Version']
+release = ..join(headers['Release'].split(.)[:-1])
+vim.command(let ver = + version)
+vim.command(let rel = + release)
+PYEND
+endif
+endfunction
+endif
+
if !exists(*s:SpecChangelog)
function s:SpecChangelog(format)
if strlen(a:format) == 0
@@ -68,6 +92,9 @@ if !exists(*s:SpecChangelog)
else
let include_release_info = 0
endif
+
+call s:GetRelVer()
+
if (chgline == -1)
let option = confirm(Can't find %changelog. Create
one? ,End of file\nHere\nCancel,3)
if (option == 1)
@@ -82,7 +109,7 @@ if !exists(*s:SpecChangelog)
endif
endif
if (chgline != -1)
- let parsed_format = * .strftime(format)
+ let parsed_format = * .strftime(format). -
.ver.-.rel
let release_info = + .name.-.ver.-.rel
let wrong_format = 0
let wrong_release = 0
--
1.8.4.474.g128a96c
--
--
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.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
vim_dev group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [PATCH] Use rpm Python library for parsing version and release info.
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 that it should be harmless for anybody without Python
support. Seriously, what could get wrong?
Matěj
pgpjCGeAJ5KT2.pgp
Description: PGP signature
