linux/poky.git/bitbake/contrib/vim/ftdetect, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

bitbake: contrib: vim: Update file detection regex

2025-11-03T17:43:31+00:00

The regex used to detect bitbake files was improved in patch 9.1.1732. Update the plugin to match that logic and fix a bug where the wrong expression was used to set the file type (Bitbake rev: 7ce0c9b44968f80a6060f9f9ff2cc00823b772cc) Signed-off-by: Joshua Watt Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

bitbake: contrib: vim: ftdetect: don't conflict with other filetypes

2025-03-03T21:38:57+00:00

Use :setfiletype instead of :set filetype. The former only sets the 'filetype' option if it has not been set before, which makes it possible to override the syntax of certain *.inc files in autocommands from e.g. .vimrc or modelines. All other ftdetect plugins in upstream vim also use :setfiletype for this reason. The detection for bitbake *.inc files is now upstream since Vim 9.0 patch 0055 [1]. If we're running an earlier Vim, use the detection heuristic from upstream [2] to overwrite the filetype explicitely if we find bitbake code. But don't always assuming that *.inc files are bitbake files so as not to break Perl, PHP, Assembly, Povray, etc. [1]: https://github.com/vim/vim/commit/fa49eb482729 [2]: https://github.com/vim/vim/blob/fb49e3cde79d/runtime/autoload/dist/ft.vim#L715 (Bitbake rev: e8efbba5d7bb4b685ed0a9b970e042ad99be8afb) Signed-off-by: Roland Hieber Signed-off-by: Richard Purdie

bitbake: contrib/vim: synchronize from kergoth/vim-bitbake rev 4225ee8b4818d7e4696520567216a3a031c26f7d

2020-07-08T11:12:45+00:00

(Bitbake rev: 24fb1f2fee449589b0c5468cbdebe9a6ffaac932) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: contrib/vim: merge changes from vim-bitbake repo

2013-09-06T21:31:33+00:00

commit 00ca441614695b4261d8d4f31b7ef0e3e3784282 Merge: 8cc367d bb88c0f Author: Christopher Larson Date: Thu Aug 22 16:42:42 2013 -0700 Merge pull request #6 from staticshock/multi-line-strings Remove "keepend" and "excludenl" directives commit bb88c0fd4ad2b7b9c8c4c73def2b3cb20c473ac3 Author: Anton Backer Date: Sat Jul 13 01:24:15 2013 -0400 Remove "keepend" and "excludenl" directives It looks like these were never actually used correctly, and were doing more harm than good. "keepend" on bbString, for instance, prevented proper nesting of ${@python} in strings. Similarly, a balanced pair of { } braces inside a shell function would force the function to terminate early if the closing brace was on its own line. So far I've seen absolutely no negative consequences from removing these, but a bunch of positive consequences. Fixes #1 commit 8cc367d01f4c699be5fcc072de59e6f2f14a138b Merge: c58628c eec6b7f Author: Christopher Larson Date: Thu Aug 22 09:46:46 2013 -0700 Merge pull request #4 from staticshock/function-names Parse function names with nested vars commit c58628ca517cd25985361fc0d27863521cc28a5d Merge: dfb0f7c a890982 Author: Christopher Larson Date: Thu Aug 22 09:43:40 2013 -0700 Merge pull request #5 from yoyko/master syntax: python expansion (${@...}) inside shell functions commit a890982b7c33a6e363b12d6cb69e22b4bbc0f317 Author: Jozef Šiška Date: Thu Aug 22 13:20:45 2013 +0200 syntax: python expansion (${@...}) inside shell functions Signed-off-by: Jozef Šiška commit eec6b7f6f0472787929f424968f9a0d78ac4af08 Author: Anton Backer Date: Fri Jul 12 22:16:01 2013 -0400 Parse function names with nested vars For instance, pkg_postinst_${PN} Fixes #3 commit dfb0f7c0d51556448cba79b474b8c19b9cded9af Author: Christopher Larson Date: Fri Jun 1 18:57:13 2012 -0400 syntax: add ?= flag def Signed-off-by: Christopher Larson commit 589a62a00709ca822a42327e7086008aba2d9933 Author: Christopher Larson Date: Fri Dec 9 22:25:47 2011 -0700 ftplugin: set commentstring Signed-off-by: Christopher Larson commit 7ffc80b3fb4ddf68cc5a69bdc63ab03d70c44f87 Author: Chris Larson Date: Thu Jun 2 15:27:48 2011 -0700 Handle +=/=+ for flags Signed-off-by: Chris Larson (Bitbake rev: f5f479bbe9b74622cd54c8d6ba8786661a3ae3e6) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

bitbake: bitbake.vim: detect *.bbappend files in ftdetect automatically

2012-12-14T13:08:48+00:00

Currently, *.bb and *.bbclass files are automatically highlighted and detected as a bitbake file. Since *.bbappend files are also bitbake files, vim plugin should automatically detect and highlight it as well. (Bitbake rev: 0668a0ea968baf930f05806a5452c8dbe4ec35ce) Signed-off-by: Richard Purdie

bitbake/contrib: Sync with bitbake upstream

2011-01-04T14:46:54+00:00

Signed-off-by: Richard Purdie

bitbake: Upgrade from 1.4 -> 1.7.4ish

2006-11-16T15:02:15+00:00

git-svn-id: https://svn.o-hand.com/repos/poky/trunk@863 311d38ba-8fff-0310-9ca6-ca027cbcb966