Tools

Solderpunk write's:
> [ ... ] So, let's spend most of our Gemini energy until June on creating
> content and tools! 

While thinking out content ideas I thought it might be nice to have some
basic tooling available. To that end I have created a highlight syntax and
file recognition for text/gemini documents when edited with Vim.

The spec for said documents is not very complex and syntax highlighting
may not be necessary, but it is nice to have to more clearly see what you
are working with.

The syntax covers everything in the current spec (preformatted blocks,
list items, headings, and links). The way it handles the url portion of a link
is extremely naive, but should work for most basic purposes (it does not
url formatting validation... any text coming after the magic string until the
next space is considered the url).

I have included a makefile for easy install into a local environment (users of
non-standard Vim implementations like SpaceVim will need to move the
files manually).

The filetype recognition recognizes files with a filetype equal to "gmi"). It is 
my understanding that that has become the common filetype. If that is not 
the case and additional support is required please let me know.

If anyone experiences any issues not spoken of in the README or has
ideas for updates or changes feel free to open an issue at the repo or
e-mail me directly.

Syntax available here:
https://tildegit.org/sloum/gemini-vim-syntax

Enjoy!

Clicking the link takes me to a 404 page.

Do have question on why vim and what windows users could do as an onramp
but this is a one man operation and you are working wjth what you use.
Mostly just wanted toreport the 404.

On Tue, Mar 3, 2020, 3:05 PM Brian Evans <b__m__e at mailfence.com> wrote:

> Solderpunk write's:
> > [ ... ] So, let's spend most of our Gemini energy until June on creating
> > content and tools!
>
> While thinking out content ideas I thought it might be nice to have some
> basic tooling available. To that end I have created a highlight syntax and
> file recognition for text/gemini documents when edited with Vim.
>
> The spec for said documents is not very complex and syntax highlighting
> may not be necessary, but it is nice to have to more clearly see what you
> are working with.
>
> The syntax covers everything in the current spec (preformatted blocks,
> list items, headings, and links). The way it handles the url portion of a
> link
> is extremely naive, but should work for most basic purposes (it does not
> url formatting validation... any text coming after the magic string until
> the
> next space is considered the url).
>
> I have included a makefile for easy install into a local environment
> (users of
> non-standard Vim implementations like SpaceVim will need to move the
> files manually).
>
> The filetype recognition recognizes files with a filetype equal to "gmi").
> It is
> my understanding that that has become the common filetype. If that is not
> the case and additional support is required please let me know.
>
> If anyone experiences any issues not spoken of in the README or has
> ideas for updates or changes feel free to open an issue at the repo or
> e-mail me directly.
>
> Syntax available here:
> https://tildegit.org/sloum/gemini-vim-syntax
>
> Enjoy!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200303/2ed5
d695/attachment.htm>

Great idea! Now I have to make an Emacs mode :)

Well I brought it up mostly because I mainly use windows (boo! Hiss! I
know... I know.) however while i neither vim or emacs having options for
both in the Great Debate is in my view good.

Worse comes to worse, install linux for windows 10 and go from there. Will
admit part of my facination with gopher is the relative simplicity of
building the pages/maps so kinda head scratching here. Then again likely
that I missed a thing somewhere about the spec where the 'how a page is
built' is spelled out.

On Tue, Mar 3, 2020 at 3:18 PM Julien Blanchard <julien at typed-hole.org>
wrote:

> Great idea! Now I have to make an Emacs mode :)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200303/7d9f
39ca/attachment.htm>

> And to poke the bear just slightly re: windows .....
> https://assets.amuniversal.com/6b08abb09fbb012f2fe600163e41dd5b

i'll have you know a friend dumpster dove for this computer as a parting
gift from boingboing's forums! (They didn't know it was a parting gift. I
just found the place a bit too uncomfortable and argument inducing.) In all
seriousness though it's a nice off lease box I'd done a few things to and I
really should reinstall one stripe of linux on or another, but then there
is the gaming that seems to not play entirely nice with linux, which is why
I hadn't bothered for a long while after my cr48 finally died (i had the
insyde bios and peppermint linux installed. It was rather nice given the
machine's limits.) Then again I tend to use nano when in command line
anyway because both vim and emacs seemed overkill (emacs, where you get an
entire environment along with your text editor ;))

> If you use another editor that supports syntax user made syntax files I'd
be happy to
> look into creating one. Let me know!
> mode :)

Only thing that springs to mind is notepad++ and I'm not sure if you can
add custom syntax definitions to it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200303/261e
ae70/attachment.htm>

On Tue, Mar 03, 2020 at 03:26:26PM -0600, Andrew Singleton wrote:
 
> Worse comes to worse, install linux for windows 10 and go from there. Will
> admit part of my facination with gopher is the relative simplicity of
> building the pages/maps so kinda head scratching here. Then again likely
> that I missed a thing somewhere about the spec where the 'how a page is
> built' is spelled out.

IMHO, building a Gemini page is even easier than building a Gophermap.
You don't need to try to remember item types, and you can just paste
URLs instead of having to tab-separate hosts, ports and paths.  It's
about as simple as can be!

Cheers,
Solderpunk