On 7/18/19 3:25 PM, Steven A. Falco wrote:
> On 7/18/19 7:44 AM, Zdenek Dohnal wrote:
>> Hi all,
>>
>> I would like to ask as Vim co-maintainer, do you find useful for Vim to do:
>>
>> - when you open new file with .spec suffix, Vim will get you basic spec
>> file structure?
>>
>> Recently I found out someone can find it as bad behavior
>> https://bugzilla.redhat.com/show_bug.cgi?id=1724126 , so I consider
>> changing the default vimrc to tell Vim 'Don't do it'.
>>
>> What's your opinion? Is it useful feature of Vim and it should stay as
>> default, or it needs to be disabled?
> I've never had a problem with it, but then I only edit rpm spec files.
>
> If you were to remove it from /etc/vimrc, would the normal syntax system 
> still provide a good way to edit rpm spec files?

Yep, AFAIK syntax while editing spec will not be changed - just
providing basic spec file structure will be removed (you will have plain
file) when you create new spec file. That could be useful for people who
creates new package from scratch though...

>
>       Steve
>
>
>
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

-- 
Zdenek Dohnal
Software Engineer
Red Hat Czech - Brno TPB-C

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to