Re: How does MacVim enable ⌘A for the call to NSOpenPanel

[Yee Cheng Chin]

Sorry, I'm not sure then. Feel free to debug MacVim itself and see if you
could bridge the difference to see why the two work differently. The code
is in MMAppController.m's fileOpen: method as I mentioned.

It's also possible that your app is eating the Cmd-A somehow. You should
make sure nothing in your app is doing key handling just for testing.


On Wed, Jan 31, 2024 at 5:52 PM Jeff Holt  wrote:

> The code I wrote does indeed set that attribute to true but ⌘ A is not
> working. Here's my MCV example that does everything except allow me to
> select all items. BTW, if I use "true" instead of "YES", then it behaves
> the same way.
>
> Multiple selections work but it won't let me select all. I would have
> expected select all to work even in the context below.
>
> #import 
>
> void openDialog () {
> @try {
> NSOpenPanel *panel = [NSOpenPanel openPanel];
> [panel setCanChooseFiles:YES];
> [panel setCanChooseDirectories:YES];
> [panel setAllowsMultipleSelection:YES];
> if ([panel runModal] == NSModalResponseOK) {
> for ( NSURL* URL in [panel URLs] ) {
> NSLog( @"%@", [URL path] );
> }
> } else {
> NSLog( @"ok button not pressed");
> }
> } @catch (NSException *exception) {
> NSLog(@"%@", [exception callStackSymbols]);
> }
> }
>
> void setup () {
> NSWindow *myWindow;
> NSRectgraphicsRect = NSMakeRect(100.0, 350.0, 400.0, 400.0);
>
> myWindow = [ [NSWindow alloc]
>initWithContentRect: graphicsRect
>  styleMask:NSWindowStyleMaskTitled
>   |NSWindowStyleMaskClosable
>   |NSWindowStyleMaskMiniaturizable
>backing:NSBackingStoreBuffered
>  defer:NO ];
>
> [myWindow setTitle:@"Open File App"];
> [myWindow makeKeyAndOrderFront: nil];
> openDialog();
> }
>
> int main (  ) {
> NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
> NSApp = [NSApplication sharedApplication];
> setup();
> [NSApp run];
> [NSApp release];
> [pool release];
> return(EXIT_SUCCESS);
> }
>
> On Wed, Jan 31, 2024 at 7:01 PM Yee Cheng Chin 
> wrote:
>
>> It's done in MMAppController.m's fileOpen: method. I think you just need
>> to enable "allowsMultipleSelection" (
>> https://developer.apple.com/documentation/appkit/nsopenpanel/1530786-allowsmultipleselection)
>> if you are trying to debug your own app.
>>
>> On Wed, Jan 31, 2024 at 2:00 PM Jeff Holt 
>> wrote:
>>
>>> I'm looking at the source for the fileOpen method and I cannot figure
>>> out how it tells NSOpenPanel to respect ⌘A to select all files in the
>>> dialog.
>>>
>>> Does anyone know how it's done?
>>>
>>> --
>>> --
>>> You received this message from the "vim_mac" 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_mac" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to vim_mac+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/vim_mac/f959c994-3e15-4184-accf-8163bea9ccd2n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vim_mac/f959c994-3e15-4184-accf-8163bea9ccd2n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> --
>> You received this message from the "vim_mac" 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_mac" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to vim_mac+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vim_mac/CAHTeOx8Gx0QUNe80EKXuxqRdBqTffH%2B5H_kgWoLy9KyO6P4LvQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/vim_mac/CAHTeOx8Gx0QUNe80EKXuxqRdBqTffH%2B5H_kgWoLy9KyO6P4LvQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> --
> You received this mes

Re: How does MacVim enable ⌘A for the call to NSOpenPanel

[Yee Cheng Chin]

It's done in MMAppController.m's fileOpen: method. I think you just need to
enable "allowsMultipleSelection" (
https://developer.apple.com/documentation/appkit/nsopenpanel/1530786-allowsmultipleselection)
if you are trying to debug your own app.

On Wed, Jan 31, 2024 at 2:00 PM Jeff Holt  wrote:

> I'm looking at the source for the fileOpen method and I cannot figure out
> how it tells NSOpenPanel to respect ⌘A to select all files in the dialog.
>
> Does anyone know how it's done?
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/f959c994-3e15-4184-accf-8163bea9ccd2n%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx8Gx0QUNe80EKXuxqRdBqTffH%2B5H_kgWoLy9KyO6P4LvQ%40mail.gmail.com.

MacVim 2023 retrospective and roadmap

[Yee Cheng Chin]

I posted this on https://github.com/macvim-dev/macvim/discussions/1472.
Cross-posting to the vim_mac email list since there are a lot of overlap
between this list and MacVim users:
--

Happy New Year! I originally wanted to send this out by EOY 2023, but
holiday mood struck me and so running a few days late. MacVim r179
 is now out,
which comes with Vim 9.1 which has also just been released. Given that I
became maintainer of MacVim ~5 years ago (see my post then
), I thought it's a good
time to do a quick retrospective and talk about what to look out for in
2024.
Retrospective 2023

For the past year, in addition to features and bug fixes, I also did some
clean up of general things such as having the website properly point to
macvim.org, having documentation available on the website, better tracking
of download counts for different versions (to help gauge if supporting a
legacy version is useful), clearer version naming, and better ways to find
out what has changed for those who don't use the binary release's built-in
updater (e.g. Homebrew). We are also getting more testing coverage for
MacVim, albeit gradually.

On compatibility, MacVim still supports down to macOS 10.9 like before, but
because of changes in Apple's developer tools, we now have to build a
separate "legacy" binary release for macOS 10.9 - 10.12 users. I don't see
an immediate reason for dropping support for these older macOS versions for
now, but CI (GitHub Actions) changes could make it harder to support in the
future. When I looked at the download counts, the legacy version for r178
has received ~1600 downloads

so far, which isn't nothing, so I'll see if we can keep it going through
other means when that happens.

MacVim also started to allow sponsors
 (#1271
) for the past 1.5
years! It will obviously continue to be free and open source, but
sponsorship does help support the project and cover some expenses and I
deeply appreciate the users who like MacVim enough to sponsor the project.
Thanks!

Small note about Touch Bar: While I personally liked the Touch Bar and have
tried to support it and make it useful within MacVim, it never seemed to
catch on within the larger macOS ecosystem. With the release of the M3
MacBook lineup in 2023, Apple has stopped making any computer that has a
Touch Bar, meaning that it is essentially a deprecated technology. MacVim
will still work with it, but there will likely be no further Touch Bar
integration work in the future for MacVim.

Also, as I have mentioned in a previous release note
, Bram
(creator of Vim) has unfortunately passed away this year. It's a great loss
for the Vim community, and I want to thank the current Vim maintainers for
stepping up and keeping the project alive.
Maintainership and community involvement

I became the maintainer 5 years ago, and looking through the priorities I
listed, I think I'm mostly happy with what was done. However, documentation
is still a little lacking, with poorly organized wikis and README; and we
still do not have great testing coverage.

The other issue was that the amount of time I had to work on MacVim
fluctuated which resulted in occasional breaks in MacVim development. One
aspect that I wish I could have handled better is to review/merge pull
requests much quicker (there are still a couple outstanding ones right now
which I'm not proud of).

In general, MacVim does not see a lot of pull requests or community
involvement, which I am trying to understand more. Does that indicate that
the project is mostly mature and doesn't need much changes? Or that it
mostly serves as a downstream project to Vim and most changes go to Vim
itself? Or that the development model makes it hard for contributors to get
their feet wet, or submit patches? If it's the latter, please feel free to
leave a comment.
Roadmap

Outside of small features and bug fixes, below are some main features of
MacVim that I want to work on in 2024. Please note that they may not all
get done by 2024 as some of these are a lot of work, but I'm hoping to at
least start work on them:

   1.

   *GPU-accelerated renderer and latency improvements* (Implement Metal
   renderer for MacVim #1262
   ): Currently MacVim is
   still rendering texts using a software Core Text renderer. Scrolling
   through a lot of texts still results in stuttering even on a new Mac. A
   hardware-accelerated renderer would also allow us to implement other
   features (e.g. smooth scrolling) as well. Also, from measuring input
   latency (using Typometer 

Re: :hardcopy not launching Preview

[Yee Cheng Chin]

I don't know why your replies got deleted Richard, but regarding your
question about encrypted files, Bram is concerned about a very specific use
case where Vim can be used to edit files in an encrypted format. See ":h
cryptmethod" and ":h :X" for example.

I personally find this to be quite an edge case. People who are paranoid
enough to edit encrypted files and need them encrypted at rest are probably
unlikely going to be printing their files out, although I could be wrong
regarding that depending on what type of content we are talking about here.
And "printexpr" has always generated temporary files (v:fname_in) to allow
for passing to a print command.

Looking around, it does seem a little hard to directly pass a PDF to
Preview to open. In theory it should definitely be possible, and you can
copy / paste to clipboard and then load it that way but then you are
exposing it to all applications. In macOS there is an ability to take a
screenshot and directly send it to Preview.app but I think there is a very
specific service (basically a way for Mac applications to advertise what
capabilities they have) and Preview.app only exposes it for TIFF image
files (which I think is how the screenshot utility sends the image to it
without saving to a file).

As for RAM file system, I think they may make it a little more secure, but
we still have a core system that the file was exposed to a global name
space (file system) that all apps can access.

Otherwise we could just load the Postscript / PDF completely in app instead
of going through an external app if we really want to.

On Sat, Jul 8, 2023 at 1:32 AM Richard Mitchell 
wrote:

> Why was my message/question deleted?
>
> On Thursday, July 6, 2023 at 5:37:25 PM UTC-4 Lifepillar wrote:
>
>> On 2023-07-06, Bram Moolenaar  wrote:
>> >
>> >> On 2023-07-04, Bram Moolenaar  wrote:
>> >> >> Or, even better, one could create a (sufficiently large) RAM disk
>> with
>> >> >> something like:
>> >> >>
>> >> >> hdiutil attach -nomount ram://204800
>> >> >> diskutil erasevolume APFS TempDisk /dev/diskN
>> >> >>
>> >> >> use it as volatile storage, then destroy it:
>> >> >>
>> >> >> diskutil eject /Volumes/TempDisk
>> >> >>
>> >> >> The RAM disk can likely be formatted with an encrypted file system,
>> too.
>> >>
>> >> I was able to do that with the following commands; there is probably
>> >> a simpler way:
>> >>
>> >> hdiutil attach -nomount ram://20480
>> >>
>> >> This will return the path to the new device, e.g., /dev/disk4.
>> >>
>> >> diskutil erasevolume APFS TempDisk /dev/disk4
>> >>
>> >> This will initialize the disk. Unfortunately, this command does not
>> >> return the volume's path, which, for some reason, is /dev/disk5s1 (I
>> >> would have expected /dev/disk4s1).
>> >>
>> >> diskutil apfs deleteVolume disk5s1
>> >> diskutil apfs addVolume disk5 APFS encrypted -nomount -stdinpassphrase
>> >>
>> >> Enter a password. Finally, mount the encrypted volume:
>> >>
>> >> diskutil apfs unlockVolume disk5s1 -stdinpassphrase
>> >>
>> >> and enter the password.
>> >
>> > Does this give a prompt, does the user know when to type the password?
>>
>> No prompt: that reads the password from stdin, then decrypts and mounts
>> the volume. If the password were to be read from a file called pwd.txt,
>> you would it in the obvious way:
>>
>> diskutil apfs unlockVolume disk5s1 -stdinpassphrase >
>> >> > I can guess that "ram://" specifies using a RAM disk. What is the
>> >> > "204800" for?
>> >>
>> >> 204800 is the number of 512-byte sectors of the disk. So, the command
>> >> above will create a 100MB RAM disk.
>> >
>> > OK, so we divide the file size by 512 and use the resulting number.
>> > Or do we need to round it up to a multiple of 1024?
>>
>> Rounding is not necessary (but it doesn't hurt), but a minimum size is.
>> About 20MB seems a safe lower bound.
>>
>> Note, however, that the commands above will create something that looks
>> and behaves like a mounted volume, including with a mount point (e.g.,
>> /Volumes/TempDisk). Even if the file system is encrypted and volatile,
>> it will still be accessible like a normal volume to anyone with access
>> to the mount point as long as the disk is mounted (usual file system
>> permissions will apply to the content).
>>
>> Is your purpose to include some macOS-specific mechanism for secure
>> inter-process communication to Vim? Maybe, that should be done using
>> some OS-specific API.
>>
>> Life.
>>
>>
>> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> 

Re: Using :Make for MacVim to invoke "Marked 2" for markdown rendering?

[Yee Cheng Chin]

I think the reason why the article you linked to uses a ftplugin file in 
.vim folder is to make sure it only gets set when you are editing a 
Markdown file. Otherwise if you do it in your own vimrc it will be set for 
all file types unless you explicitly uses a FileType auto-command to do the 
same thing. My guess is that you put the file at the wrong place, which 
resulted in it not being loaded in.

On Saturday, July 8, 2023 at 9:54:54 PM UTC-7 David Finton wrote:

> Solved.
>
> I looked for info on setting the variable makeprg in Vim.  In Vim, ":set 
> mp" showed me that the makeprg variable was still set to its default value 
> of "make". But I also realized that I could change that setting in my 
> ~/_vimrc file, rather than in a script under the ".vim" folder.  
>
> I used the same exact setting line from Rob Allen's article, but I used it 
> to set the "makeprg" variable directly in my vimrc.  
>
> Works like a charm.
>
>
> On Tuesday, July 4, 2023 at 5:27:22 PM UTC-7 David Finton wrote:
>
>> I found a simple recipe for configuring ".make" in MacVim to 
>> automatically bring up Marked 2 for markdown rendering as I edit.  I can't 
>> get it to work.  Perhaps there is a simpler way?
>>
>> The recipe is from Rob Allen:  Use Vim's :make to preview markdown 
>> 
>>
>> So I have the file ~/.vim/ftplugin/markdown.vim, and it contains the 
>> following line:
>>
>> set makeprg=open\ -a\ Marked\\\ 2.app\ '%:p'
>> When I try ":make" in MacVim, it reports the following:
>>
>> make: *** No targets specified and no makefile found.  Stop.
>>
>> I can manually start Marked 2, and in Marked 2 find the file I'm editing 
>> and open it, and that works.  But I would like to do this with a keystroke 
>> from MacVim.  Rob Allen's page filled me with hope that this was possible 
>> and easy.  Am I close?
>>
>> Thanks!
>>
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/3b27eef1-ac93-4217-a134-19ca8c8d930fn%40googlegroups.com.

Re: :hardcopy not launching Preview

[Yee Cheng Chin]

And of course you can configure MacVim / Vim to use whatever tool you want.
We are just using pstopdf by default.

On Sun, Jul 2, 2023 at 4:23 PM Yee Cheng Chin 
wrote:

> That's interesting to know about the ps2pdf difference. The default
> "pstopdf" tool that Apple ships definitely seems like the bare MVP that
> works just for people who have such needs (which is our case here) without
> them having to do too much work in supporting. FWIW I actually toyed with
> the idea of bundling  "ps2pdf" with MacVim (before I found out about the
> Mac-bundled pstopdf) before I saw the binary size… It's a pretty heavy tool.
>
> On Sun, Jul 2, 2023 at 4:03 AM Yongwei Wu  wrote:
>
>> I was unaware of the fact that pstopdf came preinstalled, otherwise I
>> would probably have used it.
>>
>> This said, I made a quick comparison, and noticed:
>>
>> - While the resulting files look similar (but not identical), the one
>> generated by ps2pdf is smaller (33537 vs 206104 bytes in my case).
>> - Ghost ps2pdf defaults to compatibility with PDF v1.4, while Apple
>> pstopdf generates a file compatible with PDF v1.3 (not configurable).
>> - They both use the Courier font, but ps2pdf embeds the PostScript
>> Type 1 font, while pstopdf embeds the TrueType font. This may be the
>> main reason for the size difference.
>>
>> Just some useless info at the weekend. ;-)
>>
>> On Thu, 29 Jun 2023 at 19:22, Richard Mitchell 
>> wrote:
>> >
>> > Advantages of ps2pdf over pstopdf ?
>>
>>
>> --
>> Yongwei Wu
>> URL: http://wyw.dcweb.cn/
>>
>> --
>> --
>> You received this message from the "vim_mac" 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_mac" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to vim_mac+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vim_mac/CADs46ic3nLvd%2Bh8NFfWWNXwBqyqiBg7KKMujC_DaRYRTXZ1tgA%40mail.gmail.com
>> .
>>
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx-tW7hx1h-xNvgiV%3DJWiNUkkGRN4G3u5ugqs%2BuAJVdxBA%40mail.gmail.com.

Re: :hardcopy not launching Preview

[Yee Cheng Chin]

That's interesting to know about the ps2pdf difference. The default
"pstopdf" tool that Apple ships definitely seems like the bare MVP that
works just for people who have such needs (which is our case here) without
them having to do too much work in supporting. FWIW I actually toyed with
the idea of bundling  "ps2pdf" with MacVim (before I found out about the
Mac-bundled pstopdf) before I saw the binary size… It's a pretty heavy tool.

On Sun, Jul 2, 2023 at 4:03 AM Yongwei Wu  wrote:

> I was unaware of the fact that pstopdf came preinstalled, otherwise I
> would probably have used it.
>
> This said, I made a quick comparison, and noticed:
>
> - While the resulting files look similar (but not identical), the one
> generated by ps2pdf is smaller (33537 vs 206104 bytes in my case).
> - Ghost ps2pdf defaults to compatibility with PDF v1.4, while Apple
> pstopdf generates a file compatible with PDF v1.3 (not configurable).
> - They both use the Courier font, but ps2pdf embeds the PostScript
> Type 1 font, while pstopdf embeds the TrueType font. This may be the
> main reason for the size difference.
>
> Just some useless info at the weekend. ;-)
>
> On Thu, 29 Jun 2023 at 19:22, Richard Mitchell 
> wrote:
> >
> > Advantages of ps2pdf over pstopdf ?
>
>
> --
> Yongwei Wu
> URL: http://wyw.dcweb.cn/
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/CADs46ic3nLvd%2Bh8NFfWWNXwBqyqiBg7KKMujC_DaRYRTXZ1tgA%40mail.gmail.com
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_RoCDsD-gggTv4Ak%2BFNiXkDey%2BCVrNSTNfM6NguO73nQ%40mail.gmail.com.

Re: :hardcopy not launching Preview

[Yee Cheng Chin]

Yup, there is no reason to not use Vim 9 for bundled scripts since we don't
have backwards compatibility to worry about.

Interesting point about using osascript,. I didn't know that. I tested it
and it does seem to block. I do want to avoid having to ask about
permissions just to print a file (since such permissions could be broad and
the user may not want to give it to begin with), and I found that I could
trick it into a weird state. In particular, if the pdf file doesn't exist
for some reason or is corrupted (I just typed "asdf" into a blank file),
you can trick Preview to pop up a dialog box (in the background) saying
that it can't open the file but *not *show the app icon in the Dock,
meaning the user has no way of finding it. The precise steps is a little
convoluted (you need to close Preview first) and to be fair we shouldn't
generate corrupt PDF files, and this actually seems more like a macOS bug
per se, but in this case the blocking behavior can actually become a
liability. I think I will stick with the timer trick for now but good to
know that osascript can block on this for future reference.

On Fri, Jun 30, 2023 at 9:58 AM Lifepillar  wrote:

> On 2023-06-30, Lifepillar  wrote:
> > On 2023-06-30, Yee Cheng Chin  wrote:
> > The fix was in https://github.com/macvim-dev/macvim/pull/1390
>
> To delete the PDF file synchronously after it has been opened in
> Preview, AppleScript can be used:
>
> system($"osascript -e 'tell app \"Preview\" to open POSIX file
> \"{v:fname_in}.pdf\"'")
> delete($"{v:fname_in}.pdf")
>
> osascript should return only after the document has been opened. Running
> that will probably ask once for permissions to access files.
>
> Life.
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/u7n1ih%2473c%241%40ciao.gmane.io
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_OArPBUZyiyyjXbxwvBrY3ABxebOsaChmogHT4ha0MKA%40mail.gmail.com.

Re: Plugin cleanup and best practice

[Yee Cheng Chin]

You basically either manage plugins yourself, or use a plugin manager like 
vim-plug.

Managing it yourself isn't hard if you know how to use Git. Just make a 
folder ".vim/pack/myplugins/start/" and then you can git clone any plugins 
into that folder you want. "myplugins" can be substituted with any name you 
want. Benefit is that it's simple and you have full control. Annoying part 
is you have to manually keep them up to date. It's not a bad option if you 
only have a few plugins you use.

Otherwise if you use something like vim-plug the benefit is you have a 
vimrc that describes all the plugins you want and it will do the work for 
you in managing them and keeping them up-to-date and selectively loading 
them.

On Saturday, May 6, 2023 at 5:48:34 AM UTC-7 Owajigbanam Ogbuluijah wrote:

> I've come to trust *junegunn/vim-plug 
> * over the years. It's got guards 
> as well to lazy-load if you need.
>
> For the systems disparity you have, you can use Vim's *has()* function to 
> guard what plugins go where.
>
> On Thu, May 4, 2023 at 8:16 PM Daryl Lee  wrote:
>
>> In a galaxy long ago and far away, I struggled with installing plugins an 
>> used pathogen to simplify the process.  Now I am up to Vim 9.0 on both my 
>> M2 Macbook Air and on my Intel iMac.  Vim-Latex works nicely on the Macbook 
>> Air but not on the iMac.  When I did a side-by-side compare of the two .vim 
>> folders, they were grossly different.  I'm on the verge of wiping out all 
>> traces of Vim on both machines and starting clean with the two or three 
>> plugins I really care about.  Where do I find the best documentation for 
>> installing plugins under Vim 9.0? 
>>
>> -- 
>> -- 
>> You received this message from the "vim_mac" 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_mac" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to vim_mac+u...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vim_mac/12f19e35-3f58-4ae5-b218-1a9c28bc3b6an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/00d4b7e7-741b-465d-9a73-e25493673819n%40googlegroups.com.

Re: :hardcopy not launching Preview

[Yee Cheng Chin]

Actually this was fixed in MacVim, but I have been busy with
different things and traveling and didn't have time to polish up a proper
release which is why you are seeing the issue :(

I pushed out a pre-release build (you can access it in the Advanced
settings or download from the MacVim release page) but I should really get
on to releasing it since it's been like 4-5 months already.

The fix was in https://github.com/macvim-dev/macvim/pull/1390 by using
pstopdf since it's bundled with macoS.

On Thu, Jun 29, 2023 at 1:07 PM Lifepillar  wrote:

> Could MacVim's gvimrc perhaps be updated to include something to this
> effect?
>
> fun! MacVimPrintFile(fname)
>   call system('/usr/bin/pstopdf ' .. fname)
>   call system('/usr/bin/open -a Preview ' .. fname .. '.pdf')
>   return v:shell_error
> endf
>
> set printexpr=MacVimPrintFile(v:fname_in)
>
> Thanks,
> Life.
>
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/u7ko9l%24khj%241%40ciao.gmane.io
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_ocRZLK5bQDms0cS-oPvoOrg3HqrWi0YE8GTDw-cr7VA%40mail.gmail.com.

Re: Getting a more readable font

[Yee Cheng Chin]

That's fair. It's ok to set encoding to utf-8. MacVim sets it for you as
default anyway so it's not necessary, but it could be useful to set that in
vimrc to maintain cross-compatibility, if you use Vim on platforms where
that is not the case.

On Fri, Apr 21, 2023 at 2:10 AM Lifepillar  wrote:

> On 2023-04-19, Tony Mechelynck  wrote:
> > On Tuesday, April 18, 2023 at 5:58:25 PM UTC+2 Yee Cheng Chin wrote:
> >
> > No, please *don't* set fileencoding, encoding, or fileformats in your
> vimrc
> > at all. That's not where those settings should go and in fact you should
> > rarely need to set these settings. The default works just fine. I
> recommend
> > reading the documentation on what each one does. Online snippets like
> > StackOverflow and great for addressing specific needs but they are not
> good
> > for setting up a vimrc cohesively.
> >
> > Setting 'encoding' etc. in the vimrc _may_ be a good idea >
>
> Thanks for this thorough description of the settings. I will only add
> that `:help encoding` in MacVim has this note:
>
> NOTE: For MacVim and GTK+, it is highly recommended to set 'encoding'
> to "utf-8".  Although care has been taken to allow different
> values of
> 'encoding', "utf-8" is the natural choice for the environment and
> avoids unnecessary conversion overhead.
>
> Best,
> Life.
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/u1rv6d%241ba%241%40ciao.gmane.io
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx8izFhyqcYVCpQ3NzxTxwWJQqf%3DD5idPdvUG%2Bg2WBznYw%40mail.gmail.com.

Re: Getting a more readable font

[Yee Cheng Chin]

No, please *don't* set fileencoding, encoding, or fileformats in your vimrc
at all. That's not where those settings should go and in fact you should
rarely need to set these settings. The default works just fine. I recommend
reading the documentation on what each one does. Online snippets like
StackOverflow and great for addressing specific needs but they are not good
for setting up a vimrc cohesively.

On Tue, Apr 18, 2023 at 12:58 AM Eric Weir  wrote:

>
> > On Apr 16, 2023, at 2:20 PM, Yee Cheng Chin 
> wrote:
> >
> > After you picked the font, the setting is only set in memory. You need
> to change your vimrc for the setting to persist. The easiest way to find
> out what the font is set to is by doing "set guifont?", which will show you
> what the font picker chose. You can copy that setting to your vimrc for it
> to stick.
>
> Somehow, something I thought I’d already done worked on a second try. Or
> so it seemed. Menlo:h14 gives me what I was groping for.
>
> Thanks,
>
> --
> Eric Weir
> Decatur, GA  USA
> eew...@comcast.net
>
> “Look deep into nature, you will understand everything better.”
>
> - Albert Einstein
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/0E4086CA--4FD4-BE2A-21EDEDD738A4%40comcast.net
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_91FgiaVmkeiWjuhPHQD97_8J7vrytTyRofvy2_oDWjA%40mail.gmail.com.

Re: "cannot convert" when trying to save .vimrc after editing

[Yee Cheng Chin]

I saw in your other email that you have a setting to set fileencoding to
"utf-10"? Why is that? Everything should really be utf-8, especially on the
Mac, unless you have *very *specific reasons not to. The error you are
seeing (type `:help E213` to find out more) is related to that.

On Sun, Apr 16, 2023 at 10:39 PM Eric Weir  wrote:

>
> After editing my .vimrc trying to make text more readable I got an error
> message—“E213: Cannot convert (add ! to write without conversion)"—when I
> tried to save the changes.
>
>
>
> --
> Eric Weir
> Decatur, GA  USA
> eew...@comcast.net
>
> "(I)t is important that awake people be awake... the darkness around us is
> deep."
>
> - William Stafford
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/A34ABAEA-DA5D-4130-B3B0-EB471E5458A6%40comcast.net
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx81etyKJhZoKCO0u_H0iscPqvTzDye11ymmKTACf0GDjA%40mail.gmail.com.

Re: Getting a more readable font

[Yee Cheng Chin]

After you picked the font, the setting is only set in memory. You need to
change your vimrc for the setting to persist. The easiest way to find out
what the font is set to is by doing "set guifont?", which will show you
what the font picker chose. You can copy that setting to your vimrc for it
to stick.

On Sun, Apr 16, 2023 at 10:15 PM Eric Weir  wrote:

>
> Typing :set guifont=* calls up the mac font picker. With the font picker
> open I get this:
>
>
> Restarting Vim I get this:
>
>
> Why are they different? How can I get the first setting to stick?
>
> Thanks,
>
>
> --
> Eric Weir
> Decatur, GA  USA
> eew...@comcast.net
>
> "(I)t is important that awake people be awake... the darkness around us is
> deep."
>
> - William Stafford
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/F996FF7B-A09B-4B6D-B3C7-F484BEF5C0DE%40comcast.net
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx8_k6Tu49Fsj7CZi3NHXH0UceJChcCBbi%3DeWV0%3DB06F-g%40mail.gmail.com.

Re: Vim Anywhere

[Yee Cheng Chin]

I think the question is whether it's only slow when using vim-anywhere
(versus opening MacVim being slow regardless). If it is only slow when
using vim-anywhere, then you should probably file an issue there and ask
them to diagnose it.

On Sun, Apr 2, 2023 at 12:49 AM Eric Weir  wrote:

>
> > On Mar 31, 2023, at 4:17 PM, Yee Cheng Chin 
> wrote:
> >
> > What Vim are you using? Since you are posting to vim_mac, I'm guessing
> it's MacVim? Is it only slow when invoked and then go back to normal? As
> in, when exactly does the issue start and end when using the plugin?
> >
> > Also, standard questions about what versions of your OS and MacVim etc.
>
> Thanks for responding. Yes, it’s MacVim. It's slow to open. Once open it
> function normally
>
> I installed it in terminal with the script provided by the developer. It
> installed in root ~/.vim-anywhere. I thought it might load more quickly if
> it was installed in my vim folder, but my vim-plug didn’t find it, even
> though it’s in a GitHub  any repository.
>
> macOs is 11.7.3, MacVim is 9.0.1276
>
>
> --
> Eric Weir
> Decatur, GA  USA
> eew...@comcast.net
>
> "(I)t is important that awake people be awake... the darkness around us is
> deep."
>
> - William Stafford
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/3962C19F-519A-4DAD-9DBE-2B01E4570916%40comcast.net
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx-Q1gA6gCudYkYa_QnjD3ws2Mmbh1pACmVPshHaWsrwpA%40mail.gmail.com.

Re: Vim Anywhere

[Yee Cheng Chin]

What Vim are you using? Since you are posting to vim_mac, I'm guessing it's
MacVim? Is it only slow when invoked and then go back to normal? As in,
when exactly does the issue start and end when using the plugin?

Also, standard questions about what versions of your OS and MacVim etc.


On Fri, Mar 31, 2023 at 1:03 AM Eric Weir  wrote:

>
> I would like to use Vim to compose and edit text in—or for—documents in
> other apps.
>
> I have Vim Anywhere.  It works
> fine. One minor issue: Vim is slow in responding when invoked.
>
> I haven’t a clue how to go about addressing it. Suggestions appreciated.
>
>
> --
> Eric Weir
> Decatur, GA  USA
> eew...@comcast.net
>
> "Imagining the other is a powerful antidote to fanaticism and hatred."
>
> - Amos Oz
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/F401E4B0-30DB-40B5-8911-170110129D02%40comcast.net
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx-PZfcoyGcm2SeoTTVix4GmznYhJQvX7-r77VDnuBqsUw%40mail.gmail.com.

Re: +sound

[Yee Cheng Chin]

Also, in case you are using MacVim specifically (since that was mentioned),
note that +sound support was merged into Vim, but not yet to the latest
release of MacVim. So if you use a public MacVim release you won't have it
*yet*. A new release (r175) for MacVim should be made soon-ish in November,
hopefully.

On Sun, Nov 13, 2022 at 8:22 AM Lifepillar  wrote:

> On 2022-11-12, Richard Mitchell  wrote:
> > I see that sound has been added to macvim!!
> >
> > What can we do with it?  Are there examples?
>
> Videogames: https://github.com/vim/killersheep :-)
>
> You may add typewriter sounds on key presses:
>
> autocmd InsertCharPre * call sound_playfile("/path/to/soundfile")
>
> With sound_playevent() you may easily play system sounds (the sounds in
> /System/Library/Sounds):
>
> call sound_playevent("Sosumi")
>
> Personally, I would really like Vim to play a sound on search wrap—but
> that does not seem easy to do.
>
> If you use Vim to build, compile, or launch (asynchronous) jobs, you may
> use sounds to signal when a job is over.
>
> Another (more or less extravagant) idea: combine with timers to make
> a “Pomodoro” (a time span for focusing on something): launch a timer
> that plays a sound 20–25 minutes from the current time.
>
> Generally speaking, I think that the main use for sounds is hook on some
> autocommand or on some callback from asynchronous jobs or timers.
>
> Hope this helps,
> Life.
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/tkr5ja%24vqp%241%40ciao.gmane.io
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx9jmo_bpmPjDcL9N2d3PgLSbUXP6-nxSaZ%3DLdPzSu8BsQ%40mail.gmail.com.

Re: Cannot load Coc Extension only in MacVim

[Yee Cheng Chin]

Another thing that I can remember off the top of my head is to check
whether this plugin works in GVim for Windows or Linux. For example, the
behavior for ":!" was changed recently for (POSIX-based systems) GVim (see
https://github.com/vim/vim/issues/8951) which could cause spawned
background processes to immediately exit after the command is done
(compared to terminal Vim where it would run in the background). If coc
uses that command to spawn processes (and don't check the results) that
could make a difference between terminal and GUI Vim.

On Thu, Sep 15, 2022 at 2:49 PM Yee Cheng Chin 
wrote:

> I don't have Coc installed and this plugin requires some set up. Are
> others seeing this as well? Can you file a GitHub issue with more detailed
> steps for a minimal repro? Otherwise it could be hard for me to know how to
> start reproducing this.
>
> You could also consider filing an issue at coc-ltex. They should know the
> codebase a lot better and able to pinpoint where the issue is (or at least
> add a more descriptive error message). Otherwise it would be a lot more
> work for us to dig through things.
>
> Other than that, it could be a permission issue. You could go to System
> Preferences → Security Settings → Privacy and see if there is a category
> where MacVim is not checked. macOS usually only asks once so if you
> rejected a permission before it may just be silently blocking things.
>
> On Wed, Sep 14, 2022 at 6:54 AM Aaron Hayman  wrote:
>
>> I've been using Coc for a while to handle linting/autocomplete/etc for a
>> variety of languages.  I recently installed `coc-ltex` to handle grammar
>> checking in markdown files. This works fine if I use vim on a markdown file
>> from the command line. The extension activates, downloads the appropriate
>> language server, and runs just fine.
>>
>> If I open a markdown file with MacVim, nothing happens. When I check
>> `:CocList extensions`, the extension is listed but not active.  Attempts to
>> activate it fail with no displayed error message.  However, if I `:echo
>> errmsg` after I try to activate the extension, I see: `E716 key not present
>> in dictionary: "2"`, although that's not much help.
>>
>> I suspect that something in MacVim is preventing the extension from
>> downloading the language server, but I don't know what it could be.
>>
>> Note: `:version` display the exact same version in both command-line vim
>> and MacVim:
>>
>> VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Jul 25 2022 08:23:03)
>> macOS version - x86_64
>> Included patches: 1-65
>>
>> --
>> --
>> You received this message from the "vim_mac" 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_mac" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to vim_mac+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vim_mac/ad2c88dc-f592-4c05-8827-f9f4c5e381fcn%40googlegroups.com
>> <https://groups.google.com/d/msgid/vim_mac/ad2c88dc-f592-4c05-8827-f9f4c5e381fcn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx-ez%3DN5jMFGigTt-rcq0fcMJG-uhXqtYitTWOEvwsM6xA%40mail.gmail.com.

Re: Cannot load Coc Extension only in MacVim

[Yee Cheng Chin]

I don't have Coc installed and this plugin requires some set up. Are others
seeing this as well? Can you file a GitHub issue with more detailed steps
for a minimal repro? Otherwise it could be hard for me to know how to start
reproducing this.

You could also consider filing an issue at coc-ltex. They should know the
codebase a lot better and able to pinpoint where the issue is (or at least
add a more descriptive error message). Otherwise it would be a lot more
work for us to dig through things.

Other than that, it could be a permission issue. You could go to System
Preferences → Security Settings → Privacy and see if there is a category
where MacVim is not checked. macOS usually only asks once so if you
rejected a permission before it may just be silently blocking things.

On Wed, Sep 14, 2022 at 6:54 AM Aaron Hayman  wrote:

> I've been using Coc for a while to handle linting/autocomplete/etc for a
> variety of languages.  I recently installed `coc-ltex` to handle grammar
> checking in markdown files. This works fine if I use vim on a markdown file
> from the command line. The extension activates, downloads the appropriate
> language server, and runs just fine.
>
> If I open a markdown file with MacVim, nothing happens. When I check
> `:CocList extensions`, the extension is listed but not active.  Attempts to
> activate it fail with no displayed error message.  However, if I `:echo
> errmsg` after I try to activate the extension, I see: `E716 key not present
> in dictionary: "2"`, although that's not much help.
>
> I suspect that something in MacVim is preventing the extension from
> downloading the language server, but I don't know what it could be.
>
> Note: `:version` display the exact same version in both command-line vim
> and MacVim:
>
> VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Jul 25 2022 08:23:03)
> macOS version - x86_64
> Included patches: 1-65
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/ad2c88dc-f592-4c05-8827-f9f4c5e381fcn%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx8na7U5b8K3aDNj1Cuvfqisdov8SP%2BQ2uvFVL0UTmLcCg%40mail.gmail.com.

Supporting older versions of macOS for MacVim (10.9 - 10.12)

[Yee Cheng Chin]

Hi macOS Vim users, just casting a wide net here. I mentioned this (future
support of older versions of macOS) in the release notes, but there may be
people who update MacVim using other methods and don't see it.

Below is copied from https://github.com/macvim-dev/macvim/discussions/1288.
If you could, reply to the GitHub discussion thread, but if you reply here
that is fine too (I don't have email list forwarding set up for MacVim):


In a philosophy borrowed from Vim, MacVim has always tried to support macOS
versions as old as possible to allow for people using these older versions
of OSX / macOS to still be able to use the latest versions of MacVim.
Currently, MacVim supports 10.9 Mavericks (released in 2013) or above,
which I believe is relatively rare among macOS software (VLC is a good
example of supporting even older versions of macOS, however). However, in
the near future, we would likely need to bump the minimum fully supported
version up to 10.13 High Sierra (released in 2017) and move towards
deprecating 10.9 - 10.12 support. If this could affect you, read on.
Rationale

The main reason why we need to think about deprecating 10.9 - 10.12 support
is that Xcode 14 will only support 10.13 or above (see release notes

and version support table ). If
we want to use new features from macOS 13.0 Ventura, we have to use Xcode
14, which would mean the generated binary won't work on older macOS.

We also use Sparkle for updating our software, and Sparkle 2 has been
bumped to only support 10.13 and above (for similar reasons). We are
currently using Sparkle 1 for now but eventually we do want to upgrade for
various features.

Other than that there are generic maintenance pains with supporting
features across this many versions, as Apple has been aggressive in
deprecating features, meaning that sometimes we have to write multiple
versions of the code. It's also hard to test on older versions of macOS
meaning that sometimes they silently break with us only finding out much
later.
Plan

Dropping 4 versions of macOS in one go is quite harsh, and as such we would
be providing "legacy" binaries when we do releases. This means there will
be a MacVim.app and a MacVim_10.9.app. I think we should still be able to
get the legacy version to update via the Sparkle updater as well using
Sparkle 1. However, because it's built separately, it's more likely to
break, and you as the user would need to be more proactive in filing issues.

Eventually though, it may be hard to build binaries for 10.9, if our CI
drops support for Xcode 13 in their hosted runners (we could investigate
other options like GitLab if there's a strong desire to keep 10.9 support /
binary release running). That likely won't happen for a couple more years,
but once that happens we may stop building binaries for 10.9 - 10.12. When
that happens 10.9 may still be supported in source code form where you need
to build MacVim manually.

I don't see any immediate technical reason why we would drop source code
support for 10.9 for now, other than the maintenance pain I mentioned
earlier. However, it's hard to see ahead too much as Apple may try to
incentivize usage of newer features (e.g. Swift UI) that makes it hard to
maintain backward compatibility in the future.
RFC / Summary

If this affects you, feel free to comment below! It's sometimes hard to get
a feel of how many users still use these older versions of macOS unless
something breaks (see #1212
). As I mentioned above,
in the immediate future 10.9 - 10.12 will still work as we still provide a
legacy build, and I would like to gather some feedbacks on this.

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx-PqGX-REF0hUN2_6X%2BfhheVrNx1XPZB1ZRiics0sstSQ%40mail.gmail.com.

Re: color syntax by default

[Yee Cheng Chin]

For defaulting to syntax on, if you have a configuration file (~/.vimrc),
you need to manually specify that in your vimrc by adding "syntax on". Vim
also comes with some better defaults (including turning syntax on) that you
could just load in in your vimrc file (type ":h defaults.vim" to see how to
do that)

Visual mode should work, how is it not working? You may want to be more
descriptive when asking for help as it's a little hard to be able to help
otherwise.

Vim can be installed via multiple ways. The default Vim installation (I
imagine that is what you have?) is installed via macOS. You can't update
that yourself as Apple manages that installation. Other popular methods
include using Homebrew to manage Vim (go to https://brew.sh for
installation instructions), or if you want a GUI just download a MacVim
binary from https://macvim-dev.github.io/macvim/ which comes with an
auto-updater to update MacVim for you.

On Sun, Apr 4, 2021 at 9:32 AM Vincent Douce LeMathoscope <
el.dou...@gmail.com> wrote:

> hi
> my vim 8.0 freshly installed does not provide syntax color by default
> i am obliged to type :syntax on at each opening of a new doc
> how can i correct this ?
>
> ps also, the "visual mode" does not seem to be effective ?
> how can i do ?
>
> also, i spent half an hour searching on internet how to update but not
> found
> if on "formulae.brew.sh" i type "vim update" in the field it does not
> give any "vim" result
>
> any help welcom…
>
> Vincent
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/7fcd522f-b1de-4c14-8bf3-0f4b7e7bfab2n%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx8f7p1t_VO7GYnmGgwtQZYKyjqOZYDcVJtj_5q__t8STA%40mail.gmail.com.

Re: Does anyone want the macvim.org domain?

[Yee Cheng Chin]

Alright just as an update, the transfer has been done. For now
https://macvim.org will still forward to the GitHub page (
https://macvim-dev.github.io/macvim/) address in the foreseeable future,
but I could just serve the web page from the domain later on.

Also updated https://github.com/macvim-dev/ to have an email address from
the domain, and should be considered the canonical place to email MacVim
devs.

On Sun, Mar 28, 2021 at 2:17 PM Benji Fisher  wrote:

> I confirmed the e-mail address, and I will follow up directly with
> YeeCheng Chin.
>
> --
> Benji Fisher
>
> On Thu, Mar 25, 2021 at 9:16 AM Yee Cheng Chin 
> wrote:
>
>> Hi, just circling back to this 5-year-old thread! I'm currently the
>> maintainer of MacVim (http://github.com/ychin), and wondering if I could
>> take over the macvim.org domain name? In the short term I will likely
>> just maintain the domain forwarding to the GitHub page, but it would allow
>> me to say set up an email address under the macvim.org domain, and also
>> have more control over it (say just for example if in the future we want to
>> move off GitHub, it would make sense to use the macvim.org domain as the
>> canonical URL for the project).
>>
>> This is the email address I use to make Git commits to MacVim, and you
>> could email me on this.
>>
>> Thanks for keeping the domain up for macvim.org all these years btw!
>>
>> -YeeCheng Chin
>>
>> On Thursday, August 18, 2016 at 12:50:35 AM UTC-7 george@gmail.com
>> wrote:
>>
>>> On Sat, Aug 6, 2016 at 6:05 PM, Benji Fisher 
>>> wrote:
>>>
>>>> On Friday, August 5, 2016 at 9:18:04 AM UTC-4, Niklas Lindström wrote:
>>>> [snip]
>>>> >
>>>> > I agree. Having http://macvim.org/ go to
>>>> https://macvim-dev.github.io/macvim/ would be great!
>>>> >
>>>> >
>>>> > Thanks to Benji for the macvim.org of old, and for now offering
>>>> this! I used to go there a lot (to download builds for the iMac G3 at work
>>>> up until at least my first iBook).
>>>> >
>>>> >
>>>> > Cheers,
>>>> > Niklas
>>>>
>>>> That looks like a consensus.  The GutHub doc recommends adding the
>>>> domain to the GitHub settings before updating the DNS.  Who has access to
>>>> do that?  My registrar (GoDaddy) does not support ANAME nor ALIAS records,
>>>> so it seems simplest to use www.macvim.org.
>>>>
>>>
>>> Per https://help.github.com/articles/troubleshooting-custom-domains/,
>>> ​I simply have a CNAME file checked in at the root of my repository,
>>> https://github.com/georgevreilly/georgevreilly.github.io/blob/master/CNAME
>>> ,
>>> which contains  www.georgevreilly.com​
>>> ​This is User Pages, rather than Project Pages, so the branch is
>>> *master*, not *gh-pages*.
>>> However, I've also made CNAME work with gh-pages:
>>> https://github.com/nwcpp/pelican-site/blob/gh-pages/CNAME
>>>
>>> I'm using NameCheap as my domain registrar, with the following DNS config
>>>
>>> Type
>>> <https://ap.www.namecheap.com/Domains/DomainControlPanel/georgevreilly.com/advancedns>
>>>
>>> Host
>>> <https://ap.www.namecheap.com/Domains/DomainControlPanel/georgevreilly.com/advancedns>
>>>
>>> Value
>>> <https://ap.www.namecheap.com/Domains/DomainControlPanel/georgevreilly.com/advancedns>
>>>
>>> TTL
>>> <https://ap.www.namecheap.com/Domains/DomainControlPanel/georgevreilly.com/advancedns>
>>>
>>> CNAME Record
>>>
>>> @
>>>
>>> georgevreilly.github.io.
>>>
>>> 30 min
>>> Remove
>>> <https://ap.www.namecheap.com/Domains/DomainControlPanel/georgevreilly.com/advancedns>
>>>
>>> CNAME Record
>>>
>>> www
>>>
>>> georgevreilly.github.io.
>>>
>>> 30 min
>>> Remove
>>> <https://ap.www.namecheap.com/Domains/DomainControlPanel/georgevreilly.com/advancedns>
>>> ​
>>>
>>>
>>>
>>> [image: --]
>>> --
>>>
>>>
>>>
>>> <https://about.me/georgevreilly?promo=email_sig_source=email_sig_medium=email_sig_campaign=external_links>
>>>
>>> george@gmail.com  Twitter: @georgevreilly
>>> <https://twitter.com/georgevreilly>
>>> *www.GeorgeVReilly.com <http://www.georgevreilly.com/>*
>>>
&g

Re: Does anyone want the macvim.org domain?

[Yee Cheng Chin]

Hi, just circling back to this 5-year-old thread! I'm currently the 
maintainer of MacVim (http://github.com/ychin), and wondering if I could 
take over the macvim.org domain name? In the short term I will likely just 
maintain the domain forwarding to the GitHub page, but it would allow me to 
say set up an email address under the macvim.org domain, and also have more 
control over it (say just for example if in the future we want to move off 
GitHub, it would make sense to use the macvim.org domain as the canonical 
URL for the project).

This is the email address I use to make Git commits to MacVim, and you 
could email me on this.

Thanks for keeping the domain up for macvim.org all these years btw!

-YeeCheng Chin

On Thursday, August 18, 2016 at 12:50:35 AM UTC-7 george@gmail.com 
wrote:

> On Sat, Aug 6, 2016 at 6:05 PM, Benji Fisher  wrote:
>
>> On Friday, August 5, 2016 at 9:18:04 AM UTC-4, Niklas Lindström wrote:
>> [snip]
>> >
>> > I agree. Having http://macvim.org/ go to 
>> https://macvim-dev.github.io/macvim/ would be great!
>> >
>> >
>> > Thanks to Benji for the macvim.org of old, and for now offering this! 
>> I used to go there a lot (to download builds for the iMac G3 at work up 
>> until at least my first iBook).
>> >
>> >
>> > Cheers,
>> > Niklas
>>
>> That looks like a consensus.  The GutHub doc recommends adding the domain 
>> to the GitHub settings before updating the DNS.  Who has access to do 
>> that?  My registrar (GoDaddy) does not support ANAME nor ALIAS records, so 
>> it seems simplest to use www.macvim.org.
>>
>
> Per https://help.github.com/articles/troubleshooting-custom-domains/,
> I simply have a CNAME file checked in at the root of my repository, 
> https://github.com/georgevreilly/georgevreilly.github.io/blob/master/CNAME
> ,
> which contains  www.georgevreilly.com 
> This is User Pages, rather than Project Pages, so the branch is *master*, 
> not *gh-pages*.
> However, I've also made CNAME work with gh-pages: 
> https://github.com/nwcpp/pelican-site/blob/gh-pages/CNAME
>
> I'm using NameCheap as my domain registrar, with the following DNS config
>
> Type 
> 
>
> Host 
> 
>
> Value 
> 
>
> TTL 
> 
>
> CNAME Record
>
> @
>
> georgevreilly.github.io.
>
> 30 min
> Remove 
> 
>
> CNAME Record
>
> www
>
> georgevreilly.github.io.
>
> 30 min
> Remove 
> 
>
>
>
> [image: --]
> -- 
>
>
>
> 
>
> george@gmail.com  Twitter: @georgevreilly 
> 
> *www.GeorgeVReilly.com * 
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/b5e5c17f-b3d2-4529-afdd-21a0bbf68f8cn%40googlegroups.com.

Re: resizing the macvim window

[Yee Cheng Chin]

As you mentioned, Vim already supports a mode where the window size is not
a strict multiples of character cell sizes, when maximized. There are
special cases in the code base to handle that already, and for the most
part maximized windows look fine. If you do "set guioptions+=k", and then
change font size, add/remove tabs etc, Vim is also going to keep the window
size fixed, and display some empty space along the borders. This is just
going to make regular windowed mode support that in MacVim as well.

I really think it will look more natural once it's rolled out. Let's say
your monitor is 1080 pixels tall and your font size is 14 pixels, that
means you will have 77 rows = 1078 pixels tall (I'm ignoring things like
windows border here). You still need to fill those 2 pixels somehow. The
current GVim (which MacVim is doing) is to let the desktop or whatever
window below the GVim window show through, which is distracting. If you let
Vim's window size be more flexible, you can fill those 2 pixels with GVim
itself which just draws the background color (this part is implementation
specific) in the bottom right and will look much more seamless. Also, in
general, I think a native application should try to respect the window
manager's will as much as possible.

Proportional font: Sure, I think that's a different discussion. The issue
here is mostly whether we want GVim to be able to fill the empty space to
the side (we are not changing the actual character cell size here).

On Fri, Mar 5, 2021 at 2:16 AM Tony Mechelynck 
wrote:

> All Vim GUIs describe their screen sizes in terms of character cells. Some
> of them (including IIRC GTK2 and GTK3; I'm not sure about Windows and I
> don't know about MacVim) fill up the whole display when you click the
> "Maximize" button in one of the top corners, but in any case this only adds
> a few unused pixels along the borders, because Vim basically works with
> fixed-size character cells, using one cell for most characters, two cells
> for "wide CJK" characters, and between one and 'tabstop' cells for a hard
> tab, but never a noninteger number of cells. Even GTK2/GTK3 gvim, which can
> use any font, look ugly when using a proportional font, because the
> character cells are still of fixed size, which means that "wider"
> characters like m look cramped while "narrower" characters like i and l
> (small I and small L) seem to be surrounded by too much empty space. This
> property of using character cells of fixed size (a size which, in GUI Vim
> like gvim and MacVim, can only be changed by changing the 'guifont'
> setting) is so basic a property of Vim (and of Legacy vi before it IIUC)
> that I expect it never to change for as long as Vim will exist.
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/e550d6e1-eaba-415c-9cc8-44134eaacd42n%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_Kj%2B4MX0Jw5TpSMBdgZH4kkr9Tbp1Zh2Yk%2Bur5mKka4g%40mail.gmail.com.

Re: resizing the macvim window

[Yee Cheng Chin]

That's because MacVim currently rounds the window size to fixed multiples
of character sizes. FWIW, I believe the built-in terminal and iTerm2 both
do the same thing.

I do want to fix it, and have some local fixes, but it needs a little more
work and testing, and I kind of want to think about whether to make it an
option/default. "guioption-k" should probably be set as well to make this
behave nicely if I add this option. You can use
https://github.com/macvim-dev/macvim/issues/948 to track progress on this.

On Thu, Mar 4, 2021 at 7:39 AM Tony Mechelynck 
wrote:

> P.S. The size of the Firefox window is measured in pixels. The size of the
> MacVim screen (not including the window decorations, whose width is
> constant) is measured in characters. This comes from the different
> philosophy of these applications and is expected.
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/68d756b9-6899-43ee-9825-c970cee9574fn%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx91QzLyKaiZQsP_Mq%3DEVBKfQcHCq-aJ8V7Ju-WP7b7g0Q%40mail.gmail.com.

Re: mview link not working with MacVim

[Yee Cheng Chin]

It seems to work for me. How is it not working for you? If you
explicitly do "/Applications/MacVim.app/Contents/Bin/mview "
what happens exactly?

On Sat, Jan 2, 2021 at 5:05 PM creiderc  wrote:

> 8.2.2164 (169)  I see the link made in
> /Applications/MacVim.app/Contents/Bin, but calling it from the command line
> doesn't work.  As a stop gap I've put "alias mview 'mvim -R' " in my .cshrc
> file and that works.  But what is wrong that the link which is already in
> place doesn't work?  Thanks.
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/b0cc3060-32d0-4010-9d78-665f3cb78dccn%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_RuZCG0qrZ_V9FYASrBZem8ruU7_nfFXf_XEQkTpdBFA%40mail.gmail.com.

Re: Vim 8.2 is released!

[Yee Cheng Chin]

Can we include a link to https://formulae.brew.sh/formula/vim as well for a
way to use a package manager to download a terminal-only version of Vim? I
believe that's the most popular one on macOS. This is similar to how we
have links to Debian packages etc on Unix (I don't think the
http://packages.debian.org/vim actually works though…). I don't know if you
want that page to really list all the package managers though or just the
major ones, but I believe most people either get Vim on macOS via Homebrew
(either regular Vim or MacVim) or just download MacVim binary releases.

On Fri, Sep 25, 2020 at 10:25 AM Bram Moolenaar  wrote:

>
> Yee Cheng Chin wrote:
>
> > macOS: If you want a GUI version of Vim on macOS, the easiest way is to
> > download MacVim (it also includes the terminal version as well) from
> > https://macvim-dev.github.io/macvim/. Otherwise if you want an
> up-to-date
> > version of terminal-only Vim, you could consider installing Homebrew
> > (package manager) and just do "brew install vim".
> >
> > Also, I don't know who maintains the website, but I think maybe
> > https://www.vim.org/download.php#mac needs an update. It is mostly
> > referring to a few currently un-maintained projects which adds to the
> > noise, and I think it may want to point people to Homebrew as the fastest
> > way to get a terminal-only version of Vim that's not MacVim. (Only
> > mentioning Homebrew because that's the most popular package manager and
> > their Vim is usually quite up-to-date, but there are probably other ones
> > too)
>
> I removed obsolte info and updated it it a bit.  Let me know if you have
> more suggestions.
>
>
> --
> The fastest way to get an engineer to solve a problem is to declare that
> the
> problem is unsolvable.  No engineer can walk away from an unsolvable
> problem
> until it's solved.
> (Scott Adams - The Dilbert principle)
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx8EMJLy5EKjS7n6WSM8XFewEMajJH3kT_-Xkd9a%2BveZOQ%40mail.gmail.com.

Re: Vim 8.2 is released!

[Yee Cheng Chin]

macOS: If you want a GUI version of Vim on macOS, the easiest way is to
download MacVim (it also includes the terminal version as well) from
https://macvim-dev.github.io/macvim/. Otherwise if you want an up-to-date
version of terminal-only Vim, you could consider installing Homebrew
(package manager) and just do "brew install vim".

Also, I don't know who maintains the website, but I think maybe
https://www.vim.org/download.php#mac needs an update. It is mostly
referring to a few currently un-maintained projects which adds to the
noise, and I think it may want to point people to Homebrew as the fastest
way to get a terminal-only version of Vim that's not MacVim. (Only
mentioning Homebrew because that's the most popular package manager and
their Vim is usually quite up-to-date, but there are probably other ones
too)


On Thu, Sep 24, 2020 at 4:18 PM Mathoscope Éveilleur de Mathématiques <
el.dou...@gmail.com> wrote:

> Hi
> i am totally beginner in bash and vim on both mac os X and also a toshiba
> running Mint
> i just wanted to know how to upgrade to 8.2 (i have 8.0)
> i dont really understand the explanations on the link given in the posts
> thanks
> Vincent
> Le jeudi 12 décembre 2019 à 16:08:18 UTC+1, Bram Moolenaar a écrit :
>
>>
>> Hello Vim users!
>>
>> Announcing: Vim (Vi IMproved) version 8.2
>>
>>
>> This is a minor release, a lot of bugs have been fixed, documentation
>> was updated, test coverage was improved, etc. There are a few
>> interesting new features, see below.
>>
>> Read the announcement with links and a few images online:
>> https://www.vim.org/vim-8.2-released.php
>>
>> Once you have installed Vim 8.2 you can find details about the changes
>> since Vim 8.2 with:
>> :help version8.2
>>
>>
>> Background
>> --
>>
>> Before I did the keynote at VimConf 2018 I asked plugin developers what
>> they wanted from Vim. The result was a very long list of requested
>> features. The top two items were clear: Popup windows and text
>> properties.
>>
>> After more than a year of development the new features are now ready for
>> the Vim crowds. Popup windows make it possible to show messages,
>> function prototypes, code snippets and anything else on top of the text
>> being edited. They open and close quickly and can be highlighted in many
>> ways. More about that below.
>>
>> This was no small effort. Although the existing window support could be
>> used, popup windows are different enough to require a lot of extra
>> logic. Especially to update the screen efficiently. Also to make it easy
>> for plugin writers to use them; you don't need to tell Vim exactly where
>> to show one, just give a reference point and the text to display, Vim
>> will figure out the size and where the popup fits best.
>>
>> Text properties can be used for something as simple as highlighting a
>> text snippet or something as complicated as using an external parser to
>> locate syntax items and highlight them asynchronously. This can be used
>> instead of the pattern based syntax highlighting. A text property sticks
>> with the text, also when inserting a word before it. And this is done
>> efficiently by storing the properties with the text.
>>
>> The new change listener support can be used to keep the highlighting
>> up-to-date and support other LSP features. An example of what can be
>> done with this is the "govim" plugin. It connects to a server (written
>> in Go) and uses "gopls", the Language Server Protocol (LSP) server for
>> Go. You can find a list of features with links to demo videos on github:
>> https://github.com/govim/govim/wiki/govim-plugin-API
>>
>>
>> Demo game
>> -
>>
>> To show what is possible with popup windows (and because I sometimes get
>> bored fixing bugs), I created a silly game. This uses popup windows that
>> move across the display, text properties to highlight the animals and
>> even sound to make it more fun! Thanks for my colleagues Greg, Martijn
>> and Shannon for making the silly sounds. You can find it on github:
>> https://github.com/vim/killersheep
>>
>>
>> Other noticeable new features
>> -
>>
>> A ":const" command for declaring a variable that cannot change:
>> const TIMER_DELAY = 400
>>
>> A Dictionary with literal keys to avoid all those quotes:
>> let options = #{width: 30, height: 24}
>>
>> A heredoc-style assignment to easily assign a list of lines to a
>> variable without quoting or line continuation:
>> let lines =<< trim END
>> line one
>> line two
>> END
>>
>> Function chaining for method calls:
>> mylist->filter(filterexpr)->map(mapexpr)->sort()->join()
>>
>> The xdiff library has been included for a much improved diff view.
>>
>> When 'incsearch' is set it also applies to ":substitute".
>>
>> "modifyOtherKeys" was added to allow mapping more key combinations.
>>
>> ConPTY support was added for Windows 10, can show full color in the
>> console.
>>
>> The MS-Windows installer supports translations, silent install and looks
>> 

Re: Dev Q: What Cocoa API/features can MacVim use now?

[Yee Cheng Chin]

Yeah, maintaining backwards compatibility on macOS is definitely a big pain
point in MacVim! Apple doesn't exactly make it easy either since they tend
to want everyone to use the latest and greatest but given Vim's philosophy,
MacVim has mostly erred on the side of caution and try to make sure it
still runs on old OS versions. Maybe it's a fool's errand as I don't get
good visibility into what % of users use which OS version (it's not like
MacVim collects telemetry from users and I have no plan to do so).

If you want to refactor the preference pane to use NSStackView, feel free
to work on that! (I just merged your PR to hide Sparkle update settings) I
do agree it will be useful and as we discussed anything 10.9+ can be used
without needing additional checks, which includes NSStackView. I think I
briefly looked into it before but my unfamiliarity with it made me drop it
half way through to work on other things. And yes, I see adding more
options in the future to expose more options instead of relying on
half-supported "defaults write" style configuration, and localization will
be very welcome, although it would require MacVim contributors to submit
translations. (I will likely send another email out in the future when I
want to do a localization push).

Thanks for helping out!

On Sun, Sep 13, 2020 at 12:34 PM sam  wrote:

> I was mostly asking to get a sense of how you think about using Cocoa APIs
> and doing development going forward. You've basically answered this well. I
> have my own Mac project and I've personally found it challenging to keep up
> with the changes Apple makes with each OS release while maintaining
> backward compatibility.
>
> I was thinking about NSStackView in the context of the Preference window.
> MacVim now has more preference options than before and may add more in the
> future. Stack views can be helpful in assuring proper alignment of the
> various controls and also handling localization since different languages
> will result in strings of different dimensions. They can also selectively
> hide sections which could be used to cleanly handle things like the
> DISABLE_SPARKLE option. I haven't implemented anything - it was more of a
> thought experiment at this point.
>
> Thank you for all the work you do on MacVim. It's a great project.
>
> On Sunday, September 13, 2020 at 3:21:22 AM UTC-7 Yee Cheng Chin wrote:
>
>> Actually, thinking about it more I think I would be ok with selective
>> usage of ARC in new files. Again, maybe chat with me first, as I'm curious
>> what the use case is, and autorelease works differently between ARC and
>> manual.
>>
>> On Sun, Sep 13, 2020 at 2:54 AM Yee Cheng Chin 
>> wrote:
>>
>>> Actually, MacVim uses new APIs all the time! For example, it supports
>>> Touch Bar which requires 10.12.2. Features that use these newer APIs do
>>> have to be optional with the correct compile-time and runtime checks,
>>> unless we make a conscious decision to update the minimal target (10.9). To
>>> be fair, MacVim is not actively tested on older macOS versions like 10.9,
>>> and so we would only know of issues if people file bugs against MacVim.
>>>
>>> I'm curious what you intend to use NSStackView for though? If it's a
>>> major feature, you may want to file a WIP PR/issue or contact us first just
>>> to get some feedbacks. MacVim's philosophy is to be the most integrated /
>>> native gVim implementation on macOS, and intentionally not bloated with
>>> non-Vim features, so I'm curious what feature would need NSStackView.
>>>
>>> ARC: It's mostly legacy. Developers' time is limited, and I think it's
>>> better to spend time on implementing other features / fixing existing bugs
>>> than converting to ARC. If you want to write new code, please use the
>>> existing memory allocation mechanism instead of ARC. The reason is the same
>>> as why companies have coding standards: inconsistencies in the codebase
>>> tends to be worse than whatever problem you are trying to fix.
>>>
>>> Thanks for contributing!
>>>
>>> On Sat, Sep 12, 2020 at 8:24 PM sam  wrote:
>>>
>>>> A couple questions about MacVim development:
>>>>
>>>> The current release (snapshot 165) of MacVim targets macOS 10.9+. Does
>>>> that mean that new code can use any Cocoa API from macOS 10.9 or before?
>>>> For example, NSStackView was introduced in macOS 10.9. MacVim doesn't
>>>> currently make use of this API, but if a potential contributor wanted to
>>>> work on a feature, could they use it?
>>>>
>>>> It also appears that MacVim does manual memory management. ARC

Re: Dev Q: What Cocoa API/features can MacVim use now?

[Yee Cheng Chin]

Actually, thinking about it more I think I would be ok with selective usage
of ARC in new files. Again, maybe chat with me first, as I'm curious what
the use case is, and autorelease works differently between ARC and manual.

On Sun, Sep 13, 2020 at 2:54 AM Yee Cheng Chin 
wrote:

> Actually, MacVim uses new APIs all the time! For example, it supports
> Touch Bar which requires 10.12.2. Features that use these newer APIs do
> have to be optional with the correct compile-time and runtime checks,
> unless we make a conscious decision to update the minimal target (10.9). To
> be fair, MacVim is not actively tested on older macOS versions like 10.9,
> and so we would only know of issues if people file bugs against MacVim.
>
> I'm curious what you intend to use NSStackView for though? If it's a major
> feature, you may want to file a WIP PR/issue or contact us first just to
> get some feedbacks. MacVim's philosophy is to be the most integrated /
> native gVim implementation on macOS, and intentionally not bloated with
> non-Vim features, so I'm curious what feature would need NSStackView.
>
> ARC: It's mostly legacy. Developers' time is limited, and I think it's
> better to spend time on implementing other features / fixing existing bugs
> than converting to ARC. If you want to write new code, please use the
> existing memory allocation mechanism instead of ARC. The reason is the same
> as why companies have coding standards: inconsistencies in the codebase
> tends to be worse than whatever problem you are trying to fix.
>
> Thanks for contributing!
>
> On Sat, Sep 12, 2020 at 8:24 PM sam  wrote:
>
>> A couple questions about MacVim development:
>>
>> The current release (snapshot 165) of MacVim targets macOS 10.9+. Does
>> that mean that new code can use any Cocoa API from macOS 10.9 or before?
>> For example, NSStackView was introduced in macOS 10.9. MacVim doesn't
>> currently make use of this API, but if a potential contributor wanted to
>> work on a feature, could they use it?
>>
>> It also appears that MacVim does manual memory management. ARC was
>> introduced well before macOS 10.9. Could new code use ARC if it is in its
>> own file and compiled with the fobj-arc flag? Is there a reason not to
>> migrate MacVim to ARC?
>>
>> --
>> --
>> You received this message from the "vim_mac" 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_mac" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to vim_mac+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vim_mac/37b2f7a4-322c-42e9-9157-e2c68222d061n%40googlegroups.com
>> <https://groups.google.com/d/msgid/vim_mac/37b2f7a4-322c-42e9-9157-e2c68222d061n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_d8XV%3DkCjEbLm%3D2s0YRbeN3MVjrSMYjm_htevvbo-zMQ%40mail.gmail.com.

Re: Dev Q: What Cocoa API/features can MacVim use now?

[Yee Cheng Chin]

Actually, MacVim uses new APIs all the time! For example, it supports Touch
Bar which requires 10.12.2. Features that use these newer APIs do have to
be optional with the correct compile-time and runtime checks, unless we
make a conscious decision to update the minimal target (10.9). To be fair,
MacVim is not actively tested on older macOS versions like 10.9, and so we
would only know of issues if people file bugs against MacVim.

I'm curious what you intend to use NSStackView for though? If it's a major
feature, you may want to file a WIP PR/issue or contact us first just to
get some feedbacks. MacVim's philosophy is to be the most integrated /
native gVim implementation on macOS, and intentionally not bloated with
non-Vim features, so I'm curious what feature would need NSStackView.

ARC: It's mostly legacy. Developers' time is limited, and I think it's
better to spend time on implementing other features / fixing existing bugs
than converting to ARC. If you want to write new code, please use the
existing memory allocation mechanism instead of ARC. The reason is the same
as why companies have coding standards: inconsistencies in the codebase
tends to be worse than whatever problem you are trying to fix.

Thanks for contributing!

On Sat, Sep 12, 2020 at 8:24 PM sam  wrote:

> A couple questions about MacVim development:
>
> The current release (snapshot 165) of MacVim targets macOS 10.9+. Does
> that mean that new code can use any Cocoa API from macOS 10.9 or before?
> For example, NSStackView was introduced in macOS 10.9. MacVim doesn't
> currently make use of this API, but if a potential contributor wanted to
> work on a feature, could they use it?
>
> It also appears that MacVim does manual memory management. ARC was
> introduced well before macOS 10.9. Could new code use ARC if it is in its
> own file and compiled with the fobj-arc flag? Is there a reason not to
> migrate MacVim to ARC?
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/37b2f7a4-322c-42e9-9157-e2c68222d061n%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_%3Dk09mZDSdU%3DmfhXLpKV20QLioZeQpG-CNgg0RzxXy3Q%40mail.gmail.com.

Re: Macvim takes over a help file

[Yee Cheng Chin]

Seems like for some reason the file was associated with MacVim. Does this
happen with other HTML files that you try to open in Finder? If that's the
case you can at least fix it by changing the default editor back to web
browser but I'm not sure why that would have happened.

On Sun, Jul 12, 2020 at 2:28 PM Blue Nose  wrote:

> Howdy,
> I am using a Nikon app and things work fine until I try to use the menu
> help option (which for the app is an html file). When I do use it, rather
> than the html file opening, Macvim starts up and opens the file.
> Can anyone tell me what is going on?
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/f47438c1-e36e-46b2-91ce-4d132047249eo%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx-jdoY6xr0cu%2BHUwSgj_30grvKTARNJ5z1HmKPZAm_qFg%40mail.gmail.com.

Re: MacVIM spontaneously quits when disk fills up and memory is under pressure

[Yee Cheng Chin]

Hmm, I don't have a good reason as to why. I think filing a Github issue is
probably a good idea to consolidate discussions. You could probably want to
get the crash logs as well (
https://apple.stackexchange.com/questions/26480/where-can-i-find-my-crash-logs)
to help diagnose the issue.

On Thu, Jun 25, 2020 at 2:24 PM James Dowdell  wrote:

> Hi Everybody!
>
> About once a month, based on my usage pattern, my disk will spontaneously
> fill up, and about that time virtual memory will start to struggle.  I get
> a force quit popup asking me to free up memory, similar to (
> https://discussions.apple.com/content/attachment/d09e499a-5cd9-45a2-a702-7a9900a8de51).
> Most applications are not effected if you respond in a few minutes, but
> MacVIM is the canary in the gold mine for some reason - not always, but
> generally, it will be the first app to die (or be killed, I can't tell),
> and will die almost immediately after such a force quit popup appears, and
> I'll lose whatever was open.  Of course usually the swp files remain
> (unless the disk had filled up some time ago and I didn't see...), but it's
> a huge pain if I have 10 or 20 vim instances open to remember which files
> were open and go recover all the sessions.
>
> If other applications also died as quickly I'd assume it's just the
> repercussions of the system running out of disk/ram, but none of several
> other applications I tend to run is so eager to die in these circumstances
> as MacVIM is.  At the first hint of trouble it will just disappear from the
> dock, and all running processes are suddenly gone with no warning.
>
> I was thinking of opening a github issue, but wanted to ask here if there
> was a simple config file I could change - or even a basic error log
> somewhere I can check - to get a better handle on this behavior?
>
> "Custom Version 8.1.2234 (161)"
> MacOS 10.13.6
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/0784fa77-7ba8-4963-af76-da99bc815af3o%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx9DXQwGGE52hoFxdu7UtQO%2B4mKFuqfDG%3D0ps8nbAYPg0w%40mail.gmail.com.

Re: Can't run nerdtree and lightline on MacOS Catalina using macvim 8.2.319

[Yee Cheng Chin]

Hmm, there are a lot of things going on here. First of all, do you have
vim-plug actually installed? Does it work in terminal Vim? You probably
want to put the plug initializations in your vimrc instead of gvimrc.
gvimrc should only be for GUI specific options.

Also, gvimrc is loaded automatically by MacVim (or any gVim). You shouldn't
need to load it in manually.

I'm not sure why you are getting a syntax error though. My guess is there
are some whitespace / newline issues, but it's hard to tell unless you
attach a file (you probably want to file an issue at
https://github.com/macvim-dev/macvim/issues instead).

On Wed, Apr 8, 2020 at 5:35 PM James Dekker  wrote:

> Am using macvim 8.2.319 (installed it by running the downloaded dmg file)
> on macOS Catalina (10.15.4).
>
> My .gvimrc file:
>
> set guifont=JetBrains\ Mono:h15
> set nu!
>
> call plug#begin('~/.vim/plugged')
> Plug 'itchyny/lightline.vim'
> Plug 'preservim/nerdtree'
> call plug#end()
>
> map  :NERDTreeToggle
>
> My When I try to load it using either:
>
> . .gvimrc
>
> or
>
> source .gvimrc
>
> It outputs the following error:
>
> -bash: .gvimrc: line 4: syntax error near unexpected token `('
> -bash: .gvimrc: line 4: `call plug#begin('~/.vim/plugged')'
>
> When I run macvim by doing this:
>
> gvim Hello.py
>
> The line numbers are set but I can't see liteline anywhere (I did do a
> PlugInstall and PlugUpdate).
>
> When I try to open NERD tree by clicking on Control-t, it states this:
>
> E492: Not an editor command: NERDTreeToggle
>
> By, the way, I don't have a .vimrc file created...
>
> Why are the NERDTree and liteline plug-ins not working on macvim?
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/caf3a56d-c658-4bd7-ac28-02dcb346db58%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_CU-HxRDFaGsSm7bmVkMrR25eh2o9y_iw6LrbcLe7q3w%40mail.gmail.com.

Re: Lose highlighting when Index.wiki is loaded from Dropbox

[Yee Cheng Chin]

Hmm that seems like an issue with how you are syncing the wiki files
across? How are you installing vimwiki and sharing the wiki files / vimrc
across different versions?

On Sat, Mar 21, 2020 at 9:43 AM Eric Weir  wrote:

>
> I have put my Vim files, including my Vimwiki files, in a Dropbox folder.
> I would like to be able to access them from both MacOS (MacVim) and iOS
> (iVim). However, when I open the Vimwiki index file (“index.wiki”) in
> either app the highlighting of links that enables navigation among Vimwiki
> files is lost. What happened? How do I restore it?
>
> Thanks
>
> 
> Eric Weir
> Decatur, GA  USA
> eew...@bellsouth.net
>
> "Imagining the other is a powerful antidote to fanaticism and hatred."
>
> - Amos Oz
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/BE8C5420-E925-41D5-B01D-6E83195A3DF2%40bellsouth.net
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx8swRzmcVHqtbYvPhrF%2BRX58EmnRsPhVB_L3%2BDju2r8yg%40mail.gmail.com.

Re: Delete key now left-expanding the selection?

[Yee Cheng Chin]

It seems to work for me. Are you talking about a Mac's "delete" key which
is usually the backspace on other computers? Or the normal Delete key? Have
you tried using "mvim --clean" to see if it's local settings?

On Thu, Jan 30, 2020 at 3:26 PM Felipe Gasper 
wrote:

> Hello,
>
> If I select a block of text in macvim then hit Delete, macvim will now
> expand the text selection leftward rather than deleting the block of text,
> as it has been doing.
>
> I _think_ I’m seeing this because I updated my MacPorts; it’s now using
> snapshot 161.
>
> This behavior doesn’t happen in GUI vim, just macvim.
>
> Is there a setting I can set so that Delete will delete the selected text?
>
> Thank you!
>
> -Felipe Gasper
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/bdd30921-5c5a-4753-abac-4bc9e2a9484b%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx8xMg2cagdJeMap5H8YgVGSMhqGx%2BNcP%3Di1ynvmFR6sNA%40mail.gmail.com.

Re: system copy with command-C without moving cursor

[Yee Cheng Chin]

The insert mode mapping should work so I'm not sure why it's not working
for you. It could be that you didn't do "aunmenu Edit.Copy" as I described
(you would be able to tell if that's the case because you will see the
"Edit" menu flash briefly).

Also, thinking more about it I think advising you to unmap Edit.Copy was
unwise. You could just remap the "Edit.Copy" menu to do the right thing for
you. Just do the following and Cmd-C should work as expected. This makes
the existing mappings work, and after the next MacVim release, Edit.Copy /
Cmd-C will be able to copy from Vim terminals out-of-the-box as well.

Basically, just add these to your vimrc instead of manually mapping :

nnoremenu Edit.Copy :

inoremenu Edit.Copy :


On Tue, Nov 12, 2019 at 12:28 PM Steve Molin  wrote:

> On Sun, Nov 10, 2019 at 12:35 AM Yee Cheng Chin 
> wrote:
> >
> > MacVim maintainer here. I think what you are looking for is similar to
> how Vim running in a terminal has two tiers of selection / copy-paste:
> Vim's own visual mode selection and yanking, versus terminal's (or tmux)
> own selection and copy-paste mechanism. For example, in most terminals you
> can hold down shift key and select using mouse to use the terminal's own
> selection scheme rather than Vim's (even with mouse=a). In fact, Vim's
> default interactions with the hosting terminal's copy-and-paste has been a
> source of contention and why Vim just changed defaults from mouse=a to
> mouse=nvi.
> >
> > Vim GUIs *kind of* have a concept of the same "system/terminal
> copy-paste" outside of visual mose / yanking that you want, but it's a
> little half-baked. Look up ":h modeless-selection" to read more. If you do
> "set mouse=" and then select texts in the GUI you are using modeless
> selection, which kind of simulates an external text selection. Annoyingly,
> you have to be in command line mode in order to copy texts (using CTRL-Y),
> so you have to type ":" to enter command-line mode first before you can
> copy the text. (Again, read the docs which provides more details)
> >
> > For the MacVim-specific part of not being able to unmap Cmd-C, that's
> because it's registered in the system for the Edit -> Copy menu item, so
> macOS will hijack it first. You can either remap the hotkey to something
> else (see ":h macmenu") or just remove the menu item (":aunmenu Edit.Copy").
> >
> > So the tldr is, do the following, and you will be able to use Cmd-C to
> copy texts when you have "set mouse=":
> >
> > aunmenu Edit.Copy
> >
> > nnoremap  :
> >
> >
> > Hope that helps!
>
>
> Thank you very much for this information! It was very helpful. I tried
> to get it to work from insert mode with "inoremap 
> :" but no luck, so I've settled on the "autocopy"
> mechanism. So I now have
>
> set mouse=
> set guioptions+=A
>
> and I'll try it for a while to see if it's "good enough".
>
> Thanks again for your help, and also for your work on MacVIm!
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/CAK-YbyCS2ipM_h%2BR03VWPpu%3D1kdoWSmfdgk%2BQ-V3xh%2BN4Nyoxg%40mail.gmail.com
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx-C3pUZMQ1DVmbXMThf6ErJce6aLxqve7HzmWjWwoRNRQ%40mail.gmail.com.

Re: system copy with command-C without moving cursor

[Yee Cheng Chin]

MacVim maintainer here. I think what you are looking for is similar to how
Vim running in a terminal has two tiers of selection / copy-paste: Vim's
own visual mode selection and yanking, versus terminal's (or tmux) own
selection and copy-paste mechanism. For example, in most terminals you can
hold down shift key and select using mouse to use the terminal's own
selection scheme rather than Vim's (even with mouse=a). In fact, Vim's
default interactions with the hosting terminal's copy-and-paste has been a
source of contention and why Vim just changed defaults from mouse=a to
mouse=nvi.

Vim GUIs *kind of* have a concept of the same "system/terminal copy-paste"
outside of visual mose / yanking that you want, but it's a little
half-baked. Look up ":h modeless-selection" to read more. If you do "set
mouse=" and then select texts in the GUI you are using modeless selection,
which kind of simulates an external text selection. Annoyingly, you have to
be in command line mode in order to copy texts (using CTRL-Y), so you have
to type ":" to enter command-line mode first before you can copy the text.
(Again, read the docs which provides more details)

For the MacVim-specific part of not being able to unmap Cmd-C, that's
because it's registered in the system for the Edit -> Copy menu item, so
macOS will hijack it first. You can either remap the hotkey to something
else (see ":h macmenu") or just remove the menu item (":aunmenu Edit.Copy").

So the tldr is, do the following, and you will be able to use Cmd-C to copy
texts when you have "set mouse=":

aunmenu Edit.Copy

nnoremap  :


Hope that helps!

On Sat, Nov 9, 2019 at 1:37 AM Tony Mechelynck 
wrote:

> On Friday, November 8, 2019 at 5:51:31 PM UTC+1, Steve Molin wrote:
>>
>> Thank you for your reply, Tony. I didn't mean to imply that the mouse
>> doesn't work beautifully, it does and I'm constantly amazed by the power of
>> Vim.
>>
>> Having tinkered with this for a couple hours, and read what I can find in
>> the manual, I think the problem is that when 'set mouse=' there are two
>> different things that can be called the "selection": you can select using
>> the Vim commands (eg vw) or using the mouse (eg double-left-click). When
>> you hit command-C MacVim will copy the Vim-command-selection to the system
>> clipboard but not the mouse-selection (presumably the same with gvim and
>> control-C in Windows and X)
>>
>> I tried unmapping command-C, hoping that would let the system process it,
>> but MacVim still processes it (eg in insert, control-v command-c then
>> results in the text "")
>>
>> p.s. For completeness, I tested with no .vimrc with the same results.
>>
>
> Hm, it seems I'm out of my depth here, you'll probably need some Mac user
> to help you (I'm on Linux).
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/c0b497cb-8083-4afa-8fbe-149a9c324e91%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx_EW8P364SNPFyw4bdkhPbXYyWdexVP0PydPNYga5giow%40mail.gmail.com.

Re: upgrade to macvim 8.1.2224 breaks YouCompleteMe

[Yee Cheng Chin]

This is now fixed and you can do software update, or grab the latest build
here: https://github.com/macvim-dev/macvim/releases

On Tue, Oct 29, 2019 at 1:13 AM Yee Cheng Chin 
wrote:

> Hi Julie, sorry it's an issue with using hardened runtime, which is a
> requirement for App Notarization (itself a soft requirement for
> distributing apps for macOS Catalina). I think I have a way to work around
> it and will release an update to address this. Meanwhile, you could
> manually build MacVim yourself, or strip the notarization / code signature
> from the app if you so wish, but if you could wait a couple days I should
> be able to push out a quick update with the correct entitlement to allow
> using scripting languages.
>
> On Mon, Oct 28, 2019 at 7:23 PM Julie Bullard 
> wrote:
>
>> I had the YouCompleteMe plugin working with my macvim distribution.  Then
>> today macvim told me that an update is available, and after updating
>> YouCompleteMe won't work.  I get an error now every time I start macvim,
>> which says "YouCompleteMe Unavailable: Unable to load Python".  Indeed it
>> seems that the updated version has no knowledge of my anaconda python
>> distribution the way it was before.  If I run from the command line "mvim
>> —version | grep python" I do see +python/dyn and +python3/dyn.
>>
>> I don't think the problem is related just to the YouCompleteMe plugin,
>> because if I open macvim and run ":py pass" or ":py3 pass" I get the
>> following error:
>>
>> E370: Could not load library
>> /opt/local/Library/Frameworks/Python.framework/Versions/3.7/Python
>> E263: Sorry, this command is disabled, the Python library could not be
>> loaded.
>> Press ENTER or type command to continue
>>
>>
>> Why does YouCompleteMe suddenly think that my python is in
>> /opt/local/Library/Frameworks/Python.framework/Versions/3.7/Python?  I did
>> not compile YouCompleteMe with that python.  Anyway, I know this is
>> probably not a forum for YouCompleteMe problems, but I thought I would just
>> check.
>>
>>
>>
>> --
>> --
>> You received this message from the "vim_mac" 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_mac" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to vim_mac+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vim_mac/bac8f4bc-e093-4282-99a5-3da083233841%40googlegroups.com
>> <https://groups.google.com/d/msgid/vim_mac/bac8f4bc-e093-4282-99a5-3da083233841%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx9szP7WvJLcH5nSYJbwiKE0GvDLMpzfoQqKkT4eONE-8Q%40mail.gmail.com.

Re: upgrade to macvim 8.1.2224 breaks YouCompleteMe

[Yee Cheng Chin]

Hi Julie, sorry it's an issue with using hardened runtime, which is a
requirement for App Notarization (itself a soft requirement for
distributing apps for macOS Catalina). I think I have a way to work around
it and will release an update to address this. Meanwhile, you could
manually build MacVim yourself, or strip the notarization / code signature
from the app if you so wish, but if you could wait a couple days I should
be able to push out a quick update with the correct entitlement to allow
using scripting languages.

On Mon, Oct 28, 2019 at 7:23 PM Julie Bullard 
wrote:

> I had the YouCompleteMe plugin working with my macvim distribution.  Then
> today macvim told me that an update is available, and after updating
> YouCompleteMe won't work.  I get an error now every time I start macvim,
> which says "YouCompleteMe Unavailable: Unable to load Python".  Indeed it
> seems that the updated version has no knowledge of my anaconda python
> distribution the way it was before.  If I run from the command line "mvim
> —version | grep python" I do see +python/dyn and +python3/dyn.
>
> I don't think the problem is related just to the YouCompleteMe plugin,
> because if I open macvim and run ":py pass" or ":py3 pass" I get the
> following error:
>
> E370: Could not load library
> /opt/local/Library/Frameworks/Python.framework/Versions/3.7/Python
> E263: Sorry, this command is disabled, the Python library could not be
> loaded.
> Press ENTER or type command to continue
>
>
> Why does YouCompleteMe suddenly think that my python is in
> /opt/local/Library/Frameworks/Python.framework/Versions/3.7/Python?  I did
> not compile YouCompleteMe with that python.  Anyway, I know this is
> probably not a forum for YouCompleteMe problems, but I thought I would just
> check.
>
>
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_mac/bac8f4bc-e093-4282-99a5-3da083233841%40googlegroups.com
> 
> .
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_mac/CAHTeOx-p9W2mwOpymG7A%2BJdnHnXf9zE3evBtfbNOH2TEBgc%3DUQ%40mail.gmail.com.

Re: After updating to 8.1.950 (155) can no longer save files to network folder

[Yee Cheng Chin]

Hi Bram, you have already merged my pull request, but I looked at the
corresponding commit in Neovim that got spawned from this change, and it
referenced this commit in libuv that has more details:
https://github.com/libuv/libuv/pull/2135

>From that commit I think we are currently missing a case for webdav because
we are not handling the case where it sets errno to "EINVAL". I think we
should probably just do what that commit does and ignore errno altogether.
The worst case is it will be slightly slower but that's only if something
is wrong anyway. Otherwise it will be whack-a-mole with random undocumented
errno's that are probably not intended to be used this way. I would think
Apple just assumes the programmer fall back to fsync if fcntl failed for
whatever reason.

I just opened a new pull request (https://github.com/vim/vim/pull/4025) to
fix this.



On Wed, Feb 20, 2019 at 10:34 AM Bram Moolenaar  wrote:

>
> > If others are curious about this, follow the thread on
> > https://github.com/macvim-dev/macvim/issues/861. A recent Vim build
> > (8.1.915) broke this.
>
> That patch was supposed to make it work better.  Does someone know why it
> causes this error?  And how to fix?
>
> --
> A radioactive cat has eighteen half-lives.
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: After updating to 8.1.950 (155) can no longer save files to network folder

[Yee Cheng Chin]

If others are curious about this, follow the thread on
https://github.com/macvim-dev/macvim/issues/861. A recent Vim build
(8.1.915) broke this.

On Tue, Feb 19, 2019 at 3:54 PM Eduardo Kortright 
wrote:

> After I upgraded MacVim to v. 8.1.950 (155) today, I can no longer save
> files to any network folder.
>
> I can still save files to folders on my local disk, but when I try to save
> to a shared (mounted as smbfs) folder, I get an error:
>
> E667: Fsync failed
>
> Changes to the file are not saved (MacVim shows the file as still
> modified).
>
> I can use the system vim (/usr/bin/vim) to edit files on network folders
> as before, and I can still save changes with no problems.
>
> I was able to save changes to files on network folders right before the
> upgrade; nothing else has changed on my machine, so the upgrade is the only
> thing I can blame for the problem.
>
> Unfortunately, I am running MacVim on my work computer, so I cannot run
> MacVim as root to see if this might be due to permissions problems (I had
> to get an admin to enter an admin password to run the update).
>
> I have restarted MacVim after removing my .vimrc file and doing
>
> defaults delete org.vim.MacVim
>
> but nothing helps.
>
> Any help would be appreciated.
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with the 'r' replace command and the US-Extended keyboard

[Yee Cheng Chin]

I filed an issue (https://github.com/macvim-dev/macvim/issues/837). Use
that link to track progress on this.

On Wed, Jan 9, 2019 at 7:16 AM Yee Cheng Chin 
wrote:

> The option still exists and is called "Draw marked text inline".
> Unchecking it will fix it as before. Did you try that?
>
> I do agree it's kind of a bug as I'm not a big fan of using advanced
> preferences to mask an implementation issue. Please file an issue at
> https://github.com/macvim-dev/macvim/issues so I can triage.
>
> Otherwise as Tony Mechelynck mentioned digraphs work too and is cross
> platform. The entry method here (Option key sequence) is a Mac-specific
> method of entry and there's still value in support that as MacVim aims to
> support native macOS features as much as possible.
>
> On Mon, Jan 7, 2019 at 5:48 AM Tony Mechelynck <
> antoine.mechely...@gmail.com> wrote:
>
>> P.S. Combining characters and precomposed characters can even be used
>> together, as in the first syllable of the dactylic hexameter scansion of
>>
>> Dǣdălŭs īntĕrĕā Krētēn lōngūmquĕ pĕrōsus
>> Ēxsĭlĭō tāctūsquĕ lŏcī nātālĭs ămōre…
>>
>> where AFAIK there is no precomposed æ with caron.
>>
>> Best regards,
>> Tony.
>>
>> --
>> --
>> You received this message from the "vim_mac" 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_mac" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to vim_mac+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with the 'r' replace command and the US-Extended keyboard

[Yee Cheng Chin]

The option still exists and is called "Draw marked text inline". Unchecking
it will fix it as before. Did you try that?

I do agree it's kind of a bug as I'm not a big fan of using advanced
preferences to mask an implementation issue. Please file an issue at
https://github.com/macvim-dev/macvim/issues so I can triage.

Otherwise as Tony Mechelynck mentioned digraphs work too and is cross
platform. The entry method here (Option key sequence) is a Mac-specific
method of entry and there's still value in support that as MacVim aims to
support native macOS features as much as possible.

On Mon, Jan 7, 2019 at 5:48 AM Tony Mechelynck 
wrote:

> P.S. Combining characters and precomposed characters can even be used
> together, as in the first syllable of the dactylic hexameter scansion of
>
> Dǣdălŭs īntĕrĕā Krētēn lōngūmquĕ pĕrōsus
> Ēxsĭlĭō tāctūsquĕ lŏcī nātālĭs ămōre…
>
> where AFAIK there is no precomposed æ with caron.
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Printing error: "PostScript file conversion failed."

[Yee Cheng Chin]

I wasn't able to reproduce this. Does this happen for any file with or
without syntax? Does printing a one-line file without syntax work? MacVim
actually doesn't do much other than passing the PostScript file generated
by Vim to Preview, but you could do ":hardcopy > ~/testhardcopy.ps" and
open that manually in Preview or other programs to see if it works.

Also, the latest version is 153 and I believe the official Homebrew formula
has been updated as well. You may want to update and see if it fixes the
issue.


On Wed, Dec 19, 2018 at 7:05 PM Jon Levy  wrote:

> I have been using MacVim for years, but just started getting an error on
> printing.  Typically, a print command from MacVim opens a Preview window
> containing the document (to be printed from that preview window).  Now, I
> am getting the preview-window error message, "PostScript file conversion
> failed," and the document does not appear.
>
> This is not affected by (1) removing my .vimrc and .vim configuration, or
> (2) the recommended command 'defaults delete org.vim.MacVim'.  I am using
> macOS 10.14.1, and MacVim 8.1.280 (151), installed through Homebrew.
>
> Any advice/insight would be greatly appreciated.  Thank you in advance!
>
> --
> --
> You received this message from the "vim_mac" 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_mac" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_mac+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

MacVim Snapshot 153 released / maintenance

[Yee Cheng Chin]

Hi MacVim users, snapshot-153 has just been released! You can download it by 
going to https://github.com/macvim-dev/macvim/releases/latest

The last two releases of MacVim were focused on fixing outstanding issues and 
getting macOS 10.14 (Mojave) support to work properly, which was challenging 
due to the way some APIs were deprecated by Apple. If you were having issues 
with Mojave and MacVim flickering a lot, please download the latest release 
which should make it a lot more usable. There are still some minor outstanding 
issues on Mojave and you can see what they are by going here 
(https://github.com/macvim-dev/macvim/issues?q=is%3Aissue+is%3Aopen+label%3A%2210.14+Mojave%22).
 Feel free to file issues if you encounter any problems.

If you don't know who I am, my name is Yee Cheng Chin and I have been asked to 
take over as the new maintainer of the MacVim project a couple months ago, and 
I will be responsible for the development of MacVim from now on. Thanks 
@splhack and @jpetrie for the work they have done up till now in maintaining 
the project.


# Priorities

Moving forward, here are some priorities for MacVim:

* Bug fixing and stabilization. There have been bugs and platform 
incompatibility that have been creeping into MacVim for a while now, and each 
OS release usually made it worse. The next few releases will focus on looking 
through the existing bugs and try to smooth them out to make MacVim the 
seamless experience that it should be. Please do file bugs on Github 
(https://github.com/macvim-dev/macvim/issues) if you see a problem.

* Improved regression testing. MacVim currently supports a large range of OS 
versions (more on that later), with different user preference settings that 
affect which renderer to use, etc. It doesn't currently have any automatic 
testing outside of the core Vim unit tests, so what has happened quite a bit 
recently were regressions that introduced bugs in some configurations (e.g. 
non-native fullscreen, or 10.12 Sierra) but not others making it not 
immediately obvious during testing. The fix would be to implement some sort of 
unit tests and automatic testing to be able to quickly guard against 
regressions to hopefully catch at least the most obvious breakage.

* Improve documentation. Clean up the wiki, contribution guide, README, 
development guide, etc.

* Implement a new renderer as the old Core Text renderer is deprecated in 
Mojave and the fix for it using buffered draw introduced some (minor) scrolling 
performance regression. This is lower in priority because the current renderer 
works for now.

* Continue to integrate native Mac features to MacVim (e.g. TouchBar support).

I would like to maintain a regular cadence in releasing (~1-2 months) to keep 
MacVim up-to-date with latest Vim and to deliver fixes to users quicker. You 
should be able to use https://github.com/macvim-dev/macvim/milestones to check 
on the progress on the individual releases.


# COMPATBILITY

One particular issue I would like to bring up is that right now MacVim's 
official release supports back to 10.8 Lion, meaning we have to support 7 OS 
versions. The code also has miscellaneous support for pre-10.8 compatibility. 
This creates a lot of ongoing costs when we try to make MacVim work for newer 
versions of OS, leading to more and more spaghetti and fragmented logic. I 
would like to officially drop support for 10.7 or below, and eventually 
investigate dropping support for 10.8/10.9. If this is an issue for you, 
*please* voice it! It's not set in stone and likely won't happen immediately.


If you have comments feel free to use this mailing list or file issues on 
Github. If there's interest I could consider opening up a chatroom on Gitter 
but I prefer not to have too many places discussions could happen.

-- 
-- 
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.