Debugging my config: filetype is set wrongly...

[tuxic]

Hi,

is there any way to pinpoint the line, which is "guilty" for
setting a wrong filetyoe somehow?

Background:
Currently I am editing troff files a lot. The extension of that files
are *.mm. *.me, *.tmac, *.ms and so on...depending on what troff macro
package will be used.

Everything works fine...except for the *.mm files. In case of reading
such a file, the filetyoe is set to "xml"...which is slightly wrong.
:)

By using an empty .vimrc I know, that the problem is somewhere inside
my original .vimrc.
Grepping for the usual suspect doesn't show anything obvious, though.

Is there any way to pinpoint the code in my vimrc, which triggers the
problem...?

Cheers!
mcc


--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20210215172822.ghzp6xpwfunjfwxj%40solfire.

[Gary Johnson-4]

On 2021-02-15, tuxic wrote:

> Hi,
>
> is there any way to pinpoint the line, which is "guilty" for
> setting a wrong filetyoe somehow?
>
> Background:
> Currently I am editing troff files a lot. The extension of that files
> are *.mm. *.me, *.tmac, *.ms and so on...depending on what troff macro
> package will be used.
>
> Everything works fine...except for the *.mm files. In case of reading
> such a file, the filetyoe is set to "xml"...which is slightly wrong.
> :)
>
> By using an empty .vimrc I know, that the problem is somewhere inside
> my original .vimrc.
> Grepping for the usual suspect doesn't show anything obvious, though.
>
> Is there any way to pinpoint the code in my vimrc, which triggers the
> problem...?

The usual way to find where an option or setting has been made is to
use :verbose, like this:

    :verbose set filetype?

Don't forget the question mark at the end.

Regards,
Gary

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20210215173921.GA24530%40phoenix.

[tuxic]

On 02/15 09:39, Gary Johnson wrote:

> On 2021-02-15, tuxic wrote:
> > Hi,
> >
> > is there any way to pinpoint the line, which is "guilty" for
> > setting a wrong filetyoe somehow?
> >
> > Background:
> > Currently I am editing troff files a lot. The extension of that files
> > are *.mm. *.me, *.tmac, *.ms and so on...depending on what troff macro
> > package will be used.
> >
> > Everything works fine...except for the *.mm files. In case of reading
> > such a file, the filetyoe is set to "xml"...which is slightly wrong.
> > :)
> >
> > By using an empty .vimrc I know, that the problem is somewhere inside
> > my original .vimrc.
> > Grepping for the usual suspect doesn't show anything obvious, though.
> >
> > Is there any way to pinpoint the code in my vimrc, which triggers the
> > problem...?
>
> The usual way to find where an option or setting has been made is to
> use :verbose, like this:
>
>     :verbose set filetype?
>
> Don't forget the question mark at the end.
>
> Regards,
> Gary
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20210215173921.GA24530%40phoenix.
>

Hi Gary,

***YOU SAVED MY DAY!***

Thanks a lot! :)

Cheers!
mcc


--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20210215174432.qomt34tcsalywmhu%40solfire.