Wednesday, January 24, 2024

Re: Any way to incorporate graphics into Gvim?

'meine' via vim_use said on Wed, 24 Jan 2024 20:44:47 +0100

>> >There are however ways to point to a picture for pre-print. When you
>> >
>> >This can eg. be done with basic markdown, see
>> >https://daringfireball.net/projects/markdown/basics at 'IMAGES'.
>> >LaTeX documents do the same.
>>
>> Yes. The TIO (Tab Indented Outline) to HTML presentation converter
>> I'm making will do this. Thanks for answering my question.
>
>For pre-print and processing take a look at `pandoc`. It is a program
>or series of software that interpretes basic input to make beautiful
>PDF.

Given my input file would be Tab Indented Outline (TIO), which of the
following allowed input formats would I use:

biblatex, bibtex, commonmark, commonmark_x, creole, csljson, csv,
docbook, docx, dokuwiki, epub, fb2, gfm, haddock, html, ipynb, jats,
jira, json, latex, man, markdown, markdown_github, markdown_mmd,
markdown_phpextra, markdown_strict, mediawiki, muse, native, odt, opml,
org, rst, rtf, t2t, textile, tikiwiki, twiki, vimwiki

t2t didn't work, it produced a PDF whose first paragraph was line
wrapped instead of respecting the newlines in my TIO. The default
markdown input format didn't work: On a short outline it removed the
indentation, and on a long outline it took forever (over 3 minutes) to
compile, so I Ctrl+C'ed out.

Thanks,

SteveT

Steve Litt

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20240124172945.22f49557%40mydesk.domain.cxm.

No comments: