On 5 May 2015 at 12:09, Dan Allen <[email protected]> wrote:
> I'd like to move forward with this change (not only because we're starting
> to get issues about the Vim syntax filed in random places).
>
> I've setup the repository.
>
> https://github.com/asciidoc/vim-asciidoc
>
> The next step is to submit a pull request to import the Vim syntax files.
> The problem is, I don't know if we decide what the source should be. Perhaps
> we can start by importing the source folder that's currently in the asciidoc
> repository (preserving the history), then allow development to proceed from
> there with the new stuff by Alex, Dag, etc.
>
> If no one objects, I'll begin by importing the history of the vim folder
> from the asciidoc repository as a starting point.

Should the repository be for all bindings, I guess that depends on if
any other editors/IDEs have separate bindings?

Things like the Geany asciidoc support are coded in, so not sensible
to try to add here, but emacs?, sublime? etc

Cheers
Lex


>
> -Dan
>
> On Fri, Feb 6, 2015 at 9:05 AM, Alex Efros <[email protected]> wrote:
>>
>> Hi!
>>
>> On Tue, Feb 03, 2015 at 02:47:37PM +0100, Dag Wieers wrote:
>> > In my opinion, the default asciidoc vim file must provide the best user
>> > experience as possible, this means showing bold as bold, italic as
>> > italic,
>> ...
>> > However if your view is the consensus then I don't mind maintaining my
>> > own.
>>
>> I don't see any conflict here. Syntax file shouldn't include this, but we
>> can provide both asciidoc's syntax and colorscheme as separate files.
>>
>> Main issue with colorscheme is what it should be very different for at
>> least 3 use cases - Vim on limited 8-16 color text terminals, Vim on
>> modern 256-color text terminals and GVim. Because it doesn't makes much
>> sense to use italic in first two cases where it doesn't really looks like
>> "italic" anyway.
>>
>> --
>>                         WBR, Alex.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "asciidoc" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/asciidoc.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Dan Allen | http://google.com/profiles/dan.j.allen
>
> --
> You received this message because you are subscribed to the Google Groups
> "asciidoc" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/asciidoc.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.

Reply via email to