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
>> >>
>>
On 2023-07-04, Bram Moolenaar wrote:
>
>> On 2023-07-03, Bram Moolenaar wrote:
>> > I suppose encrypting the file won't be possible, since the reader does
>> > not know how to decrypt it. Or does the Preview app support encryption
>> > somehow?
>>
>> Yes, macOS's Preview supports (at least
On 2023-07-03, Bram Moolenaar wrote:
> I suppose encrypting the file won't be possible, since the reader does
> not know how to decrypt it. Or does the Preview app support encryption
> somehow?
Yes, macOS's Preview supports (at least some?) encrypted PDFs. I did
a quick test by encrypting a
On 2023-06-30, Yee Cheng Chin wrote:
> 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.
Maybe `activate` can help there?
system($"osascript -e 'tell
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 \"P
On 2023-06-30, Yee Cheng Chin wrote:
> Actually this was fixed in MacVim
Great! Glad to see that MacVim has embraced Vim 9 script. And I will
borrow your timer trick for my own vimrc.
Thanks,
Life.
--
--
You received this message from the "vim_mac" maillist.
Do not top-post! Type your reply
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.
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
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
On 2022-05-11, Eric Weir wrote:
>
>I don’t know how to access iCloud Drive from MacVim. It doesn’t show up
>in the directory list when I do netrw.
The path to the iCloud drive should be:
/Macintosh HD//Library/Mobile Documents.
("Macintosh HD" is the default name of your computer's disk:
On 2022-05-11, Eric Weir wrote:
>
> Attempting to get Vim-Plug set up in my MacVim installation. I’ve got
> the script in ~/vim/autoload and the call to it and my plugins list in
> my .vimrc. However when I issue PlugInstall the process aborts with
> this error message:
>
> xcrun: error: invalid
On 21/02/2017 21:16, Bob Stodola wrote:
On Wednesday, February 15, 2017 at 3:32:40 AM UTC-5, Lifepillar wrote:
On 15/02/2017 09:26, Lifepillar wrote:
It's `set number`. If you have `set number` in your vimrc, Vim won't
crash.
...won't crash Terminal.app, that is.
Also, you need `set wrap
On 15/02/2017 09:26, Lifepillar wrote:
It's `set number`. If you have `set number` in your vimrc, Vim won't
crash.
...won't crash Terminal.app, that is.
Also, you need `set wrap`.
Life.
--
--
You received this message from the "vim_mac" maillist.
Do not top-post! Type your r
On 15/02/2017 09:13, Lifepillar wrote:
On 14/02/2017 16:09, Stuart Levy wrote:
On Tuesday, January 31, 2017 at 4:28:17 PM UTC-6, Peter Shenkin wrote:
Could somebody please say what they have to do to trigger this crash?
(I'm on Sierra 10.12.3 now, but never saw it earlier in 10.12.1.)
Having
On 14/02/2017 16:09, Stuart Levy wrote:
On Tuesday, January 31, 2017 at 4:28:17 PM UTC-6, Peter Shenkin wrote:
Could somebody please say what they have to do to trigger this crash? (I'm on Sierra 10.12.3 now, but
never saw it earlier in 10.12.1.) Having said that, I usually just run "mvim ",
15 matches
Mail list logo
