[vim/vim] Move files are not recognized (PR #11947)

3 views
Skip to first unread message

Amaan Qureshi

unread,
Feb 4, 2023, 4:26:17 PM2/4/23
to vim/vim, Subscribed

https://github.com/move-language/move
Problem: Move files are not recognized.
Solution: Add a pattern for Move files. (Amaan Qureshi)


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/11947

Commit Summary

  • 9175a29 Move files are not recognized

File Changes

(2 files)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/11947@github.com>

codecov[bot]

unread,
Feb 4, 2023, 4:36:21 PM2/4/23
to vim/vim, Subscribed

Codecov Report

Merging #11947 (9175a29) into master (7a1bdae) will decrease coverage by 0.83%.
The diff coverage is n/a.

@@            Coverage Diff             @@

##           master   #11947      +/-   ##

==========================================

- Coverage   81.90%   81.08%   -0.83%     

==========================================

  Files         164      154      -10     

  Lines      193675   183242   -10433     

  Branches    43787    41363    -2424     

==========================================

- Hits       158634   148579   -10055     

+ Misses      22215    21704     -511     

- Partials    12826    12959     +133     
Flag Coverage Δ
huge-clang-none 82.62% <ø> (-0.01%) ⬇️
huge-gcc-none ?
huge-gcc-testgui ?
huge-gcc-unittests 0.29% <ø> (ø)
linux 81.08% <ø> (-1.26%) ⬇️
mingw-x64-HUGE ?
mingw-x86-HUGE ?
windows ?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/if_perl.xs 54.50% <0.00%> (-17.82%) ⬇️
src/regexp_nfa.c 80.52% <0.00%> (-9.15%) ⬇️
src/arabic.c 85.86% <0.00%> (-8.70%) ⬇️
src/typval.c 82.00% <0.00%> (-7.99%) ⬇️
src/regexp_bt.c 78.52% <0.00%> (-7.46%) ⬇️
src/vim9execute.c 82.32% <0.00%> (-6.96%) ⬇️
src/json.c 77.84% <0.00%> (-5.47%) ⬇️
src/vim9instr.c 76.94% <0.00%> (-4.96%) ⬇️
src/vim9compile.c 86.70% <0.00%> (-4.54%) ⬇️
src/cmdexpand.c 86.52% <0.00%> (-4.37%) ⬇️
... and 136 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/11947/c1416855393@github.com>

Bram Moolenaar

unread,
Feb 7, 2023, 3:18:49 AM2/7/23
to vim/vim, Subscribed


> https://github.com/move-language/move
> Problem: Move files are not recognized.
> Solution: Add a pattern for Move files. (Amaan Qureshi)

Is there a better name than "move"?
Without that github link it is very hard to find information about it.

--
From "know your smileys":
:-| :-| Deja' vu!

/// Bram Moolenaar -- ***@***.*** -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/11947/c1420368798@github.com>

Amaan Qureshi

unread,
Feb 7, 2023, 12:50:52 PM2/7/23
to vim/vim, Subscribed

searching for "move language" gives me information on it..

there's this too for reference: https://move-book.com/


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/11947/c1421202014@github.com>

Bram Moolenaar

unread,
Feb 7, 2023, 2:38:23 PM2/7/23
to vim/vim, Subscribed

Closed #11947 via 6642982.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/11947/issue_event/8461507017@github.com>

Bram Moolenaar

unread,
Feb 7, 2023, 2:39:41 PM2/7/23
to vim/vim, Subscribed


> searching for "move language" gives me information on it..
>
> there's this too for reference: https://move-book.com/

I suppose it's best to just call it "move" then. "movelang" would be
more specific, but inconsistent with other filetype names.


--
From "know your smileys":
:-* A big kiss!


/// Bram Moolenaar -- ***@***.*** -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/11947/c1421342269@github.com>

Amaan Qureshi

unread,
Feb 7, 2023, 3:59:20 PM2/7/23
to vim/vim, Subscribed

searching for "move language" gives me information on it..

there's this too for reference: https://move-book.com/

I suppose it's best to just call it "move" then. "movelang" would be
more specific, but inconsistent with other filetype names.

--
From "know your smileys":
:-* A big kiss!

/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net \


/// \
\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\ help me help AIDS victims -- http://ICCF-Holland.org ///

agreed, thanks!


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/11947/c1421438285@github.com>

Reply all
Reply to author
Forward
0 new messages