zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Vim yodl syntax highlighting
Date: Fri, 10 Jul 2015 17:01:34 -0700	[thread overview]
Message-ID: <150710170134.ZM10499@torch.brasslantern.com> (raw)
In-Reply-To: <20150710181428.GH1869@tarsus.local2>

On Jul 10,  6:14pm, Daniel Shahaf wrote:
}
} > [...] 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)?

Portability, to use your parenthetical definition thereof.

} 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

In case not clear, it's not Doc/editorconfig/, it's a Doc/.editorconfig
file intended to be loaded by editors that use that common configuration
method.  I'm not in favor of adding a (non-hidden, as in not a dotfile)
tree of stuff under Doc/ that is not part of the actual documentation.

(That's a lot of nots.)

If you can't jam it all in a .vimrc or the like, it should probably go
in Util/ rather than Doc/.


  reply	other threads:[~2015-07-11  0:01 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
2015-07-11  0:01     ` Bart Schaefer [this message]
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=150710170134.ZM10499@torch.brasslantern.com \
    --to=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).