On Thu, 2019-01-10 at 10:23 +0100, Erik Skultety wrote:
> On Wed, Jan 09, 2019 at 07:35:54PM +0100, Andrea Bolognani wrote:
> > Vim won't recognize them, and thus not enable niceties
> > such as syntax highlighting, otherwise.
>
> So, is there a strict reason for the *inc.am naming? Reading throug
On Thu, Jan 10, 2019 at 11:15:43AM +0100, Erik Skultety wrote:
> On Thu, Jan 10, 2019 at 10:05:49AM +, Daniel P. Berrangé wrote:
> > On Thu, Jan 10, 2019 at 10:23:07AM +0100, Erik Skultety wrote:
> > > On Wed, Jan 09, 2019 at 07:35:54PM +0100, Andrea Bolognani wrote:
> > > > Vim won't recognize
On Thu, Jan 10, 2019 at 10:05:49AM +, Daniel P. Berrangé wrote:
> On Thu, Jan 10, 2019 at 10:23:07AM +0100, Erik Skultety wrote:
> > On Wed, Jan 09, 2019 at 07:35:54PM +0100, Andrea Bolognani wrote:
> > > Vim won't recognize them, and thus not enable niceties
> > > such as syntax highlighting,
On Thu, Jan 10, 2019 at 10:23:07AM +0100, Erik Skultety wrote:
> On Wed, Jan 09, 2019 at 07:35:54PM +0100, Andrea Bolognani wrote:
> > Vim won't recognize them, and thus not enable niceties
> > such as syntax highlighting, otherwise.
>
> So, is there a strict reason for the *inc.am naming? Reading
On Wed, Jan 09, 2019 at 07:35:54PM +0100, Andrea Bolognani wrote:
> Vim won't recognize them, and thus not enable niceties
> such as syntax highlighting, otherwise.
So, is there a strict reason for the *inc.am naming? Reading through [1] gave me
the necessary background, but is there an inherent i
Vim won't recognize them, and thus not enable niceties
such as syntax highlighting, otherwise.
Signed-off-by: Andrea Bolognani
---
src/access/Makefile.inc.am | 2 ++
src/admin/Makefile.inc.am | 2 ++
src/bhyve/Makefile.inc.am | 2 ++
src/conf/Makefile.inc.am| 2 ++
src/c
