Thanks for the reply! Your response makes compete sense.
Even my question about my message getting deleted, got deleted. Odd.
On Sunday, July 9, 2023 at 4:46:28 AM UTC-4 Yee Cheng Chin wrote:
> I don't know why your replies got deleted Richard, but regarding your
> question about encrypted
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
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:
>
I've gotten lost in this discussion. The question was just initially about
getting the functionality of using Preview back instead of sending directly
to a printer.
This has turned into a deeper discussion about file security and making
sure the PDF is encrypted. Are people auto encrypting
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
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
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, 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
No objection at all. I said it was just "some useless info at the weekend". ;-)
On Mon, 3 Jul 2023 at 07:24, Yee Cheng Chin wrote:
>
> 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
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
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
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
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
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
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
Thanks!!
On Thursday, June 29, 2023 at 11:02:20 PM UTC-4 Yee Cheng Chin wrote:
> 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
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
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.
Advantages of ps2pdf over pstopdf ?
The latter comes with OSX -> /usr/bin/pstopdf
and even got updated on 2023-06-15, so it isn't something
leftover/forgotten.
On Thursday, June 29, 2023 at 2:57:34 AM UTC-4 Yongwei Wu wrote:
> Anyway, I created a solution.
>
> Assuming you have ps2pdf
Anyway, I created a solution.
Assuming you have ps2pdf installed (Homebrew ghostscript has it). You can
add a vim_preview file:
#!/bin/sh
psfile=$1
pdffile=`echo $psfile|sed -E 's/(\.ps)?$/\.pdf/'`
ps2pdf $psfile $pdffile
open -a Preview $pdffile
Then, you can add this to your .gvimrc (not
Actually it is not a bug of MacVim.
Using techniques described in
https://vi.stackexchange.com/questions/6887/where-does-macvim-send-its-printed-files
I have located the file output by Vim. Opening the file by Preview
does not succeed. A search confirmed this:
Many thanks for the :TOhtml suggestion.
I now find that "Build-in printing" using :hardcopy is listed under
"16. Known bugs/missing features" in the MacVim Reference Manual.
On Wednesday, June 28, 2023 at 8:40:24 PM UTC-6 Yongwei Wu wrote:
> I can reproduce this behaviour on Ventura.
>
> I
I can reproduce this behaviour on Ventura.
I would suggest a workaround. You may use ":TOhtml", and then print
the HTML file from a browser.
On Thu, 29 Jun 2023 at 06:30, Kenneth R. Beesley wrote:
>
> I've been using MacVim for years, but just recently I've noticed that when I
> invoke
I'm on a new-this-year MacBook Pro, running Century 13.4.1.
On Wednesday, June 28, 2023 at 4:30:47 PM UTC-6 Kenneth R. Beesley wrote:
> I've been using MacVim for years, but just recently I've noticed that when
> I
> invoke :hardcopy, either directly or through the pulldown File > Print,
>
I've been using MacVim for years, but just recently I've noticed that when I
invoke :hardcopy, either directly or through the pulldown File > Print,
it's not
launching Preview (which allows you to select the printer, choose the
number of
copies to print, etc.). Even more mysterious, it seems
27 matches
Mail list logo
