All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9466] New: VIM_REMOVE_DOCS removes rgb.txt
Date: Mon, 05 Dec 2016 09:07:33 +0000	[thread overview]
Message-ID: <bug-9466-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=9466

            Bug ID: 9466
           Summary: VIM_REMOVE_DOCS removes rgb.txt
           Product: buildroot
           Version: 2016.11
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: sir.ferdek+buildroot at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

package/vim/vim.mk

define VIM_REMOVE_DOCS
        find $(TARGET_DIR)/usr/share/vim -type f -name "*.txt" -delete
endef

This removes file rgb.txt which is used by vim in syntax coloring.
Then, when vim tries to color it's output, you could see something in the sort
of:

Error detected while processing /usr/share/vim/vim80/syntax/syncolor.vim: 
line 46: 
E254: Cannot allocate color SlateBlue 
Press ENTER or type command to continue

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2016-12-05  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05  9:07 bugzilla at busybox.net [this message]
2016-12-05  9:31 ` [Buildroot] [Bug 9466] VIM_REMOVE_DOCS removes rgb.txt bugzilla at busybox.net
2016-12-05 20:36 ` bugzilla at busybox.net
2016-12-05 21:56 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-9466-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.