From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: Vim yodl syntax highlighting
Date: Fri, 10 Jul 2015 18:14:28 +0000 [thread overview]
Message-ID: <20150710181428.GH1869@tarsus.local2> (raw)
In-Reply-To: <150706153158.ZM4229@torch.brasslantern.com>
Bart Schaefer wrote on Mon, Jul 06, 2015 at 15:31:58 -0700:
> On Jul 6, 2:12pm, Daniel Shahaf wrote:
> }
> } Should this live in the zsh repository? If it's useful to people it
> } should live alongside the code, but if it's just me, I'll throw it on my
> } personal github account.
>
> There are presently
>
> .editorconfig
> Src{,/{Modules,Builtins,Zle}}/.exrc
>
> already in the distribution, so there would be some precedent for putting
> this in Doc/ if there were a reasonably portable way to make it load (or
> not) as required/supported by the local vi-alike.
What's your concern — portability (not causing errors for people who use
other vi-like editors) or usability (automatically enabling the syntax
highlighting)?
Compatibility with vi isn't an issue: these are Vim scripts, vi won't
see them and won't try to execute them in the first place.
Compatibility with Vim builds that don't support syntax highlighting...
I think this can be made to work.
Automatically enabling syntax highlighting: I don't believe Vim has
built-in support for letting a directory tree specify its own syntax
highlighting, so I assume _some_ opt-in step would be needed. We could
make this as frictionless as possible, for example, by putting the file in
Doc/editorconfig/vim/syntax/zyodl.vim
and having a
Doc/editorconfig/vim/filetype.vim
that installs filetype-detection for the zyodl filetype; this way,
people will be able to get syntax highlighting simply by adding
Doc/editorconfig/vim/ to their 'runtimepath' setting (aka, a one-line
~/.vimrc change).
Perhaps there's a better way; I'm open to suggestions from the audience.
> I have an ancient but still functional yodl-mode.el around, somewhere.
Obviously we can't have _that_ in the repository :-)
next prev parent reply other threads:[~2015-07-10 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 14:12 Daniel Shahaf
2015-07-06 18:46 ` Jason Spiro
2015-07-06 19:02 ` Jason Spiro
2015-07-10 17:57 ` Daniel Shahaf
2015-07-06 22:31 ` Bart Schaefer
2015-07-10 18:14 ` Daniel Shahaf [this message]
2015-07-11 0:01 ` Bart Schaefer
2015-07-12 6:51 ` [PATCH] " Daniel Shahaf
2015-07-13 15:08 ` Bart Schaefer
2015-07-13 23:16 ` Daniel Shahaf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150710181428.GH1869@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).