Path: csiph.com!4.us.feeder.erje.net!feeder.erje.net!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Michal Pesa Newsgroups: gnu.bash.bug Subject: Re: Lacking documentation of colored-completion-prefix Date: Tue, 31 Jul 2018 18:17:27 +0200 Lines: 16 Approved: bug-bash@gnu.org Message-ID: References: <05b133b9-6a94-1ad0-4df4-f44954ef45d8@gmail.com> <835fffbf-3770-6a51-d7d6-b232d0fe3b00@case.edu> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1533053858 25708 208.118.235.17 (31 Jul 2018 16:17:38 GMT) X-Complaints-To: action@cs.stanford.edu To: chet.ramey@case.edu, bug-bash@gnu.org Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=ngy5XyX9UziE0nXVWR62r3J2NlZi8G5aM3uvLN1V2k0=; b=sD/KHcE7IkRpWAH9gggu0ZY7pt8MJAf6uJsyCAc+dlRUkgM8OCJqNdYu7unAvCYWmJ QTUWj08lKdkiOplOOPhDIak1qm2h/odSX/i0K/tPmMo+iyZdBc7+0xm+ag8w5RBnOnKC Y7NTv3X45Kmois+TcmgyCsBZ4nM9tBS0vXTmuqQzvFmiKq6f6zKK9Gq2GQnI/KdYnb1n gmDr+d4/k+NPOH0CTfpiyXFkmQBd1fDi/iryWNTbWs5U3lktAr9T82Zic5CfwQG7L7SJ kJZW/34NwkOP3dlxyQxDz8DTvg27VOS4ZuUG+lDXdLGg6KWXHCFCXaaLMIAAi6cisQcB FneQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ngy5XyX9UziE0nXVWR62r3J2NlZi8G5aM3uvLN1V2k0=; b=VRd5gk71+NWlzj9qGpTPX7SsGGizOIHtVuL6/qUE0XDjfPJBs9UqQ9R0zQJ9XaWD1B 0uWh79q/5wL8VOiNxoLGbWuHyS4vkHwpf0bj/2moyZBPs4+JYXV0BqLeuhFMmPCL9nsP 9YApDis2Z6D58eoxj4KYwqdslQT02JPVdCbJ6BDBz/DiA9mj/0eA4zrSUCJVq47gzMYh WV+88yXa7ghmbxaDb/RhFjCeSRmYpZ8v1++xyf7uNs9kBr8oYJDTu2/BHhCVBgewAHvH UBaXAB1zlAK/H84XbI2QwZSvNJDOGQG0G5qsjn3h3L32Its6x0RejYm8jecOJDt8qcCK Q/4Q== X-Gm-Message-State: AOUpUlEVD22eE6+q6jVbd+Relx6BNZjTJVRgtuhxvy1FbV6N1CvbQk02 qyVKn/zPoUklfh7IaGS2N16uknCH X-Google-Smtp-Source: AAOMgpeFIPTRGW6ODeOb4aLpjAvWHOWZJMLXBhyvWHoMrCHAt+YCrVPHQKk5gGz4rdHZ9IMeW83sAQ== X-Received: by 2002:adf:9aeb:: with SMTP id a98-v6mr21038038wrc.110.1533053848287; Tue, 31 Jul 2018 09:17:28 -0700 (PDT) User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 In-Reply-To: <835fffbf-3770-6a51-d7d6-b232d0fe3b00@case.edu> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::42e X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:14425 That's exactly what I would welcome in the manual. Something as simple as: The socket color "so" of the LS_COLORS variable is used as the prefix color. Regards. On 7/31/2018 5:09 PM, Chet Ramey wrote: > On 7/25/18 2:48 PM, Michal Pesa wrote: >> It would be obvious then what color exactly needs to be change in the >> LS_COLORS variable if a different color was desired. > I don't see setting the color in stone as helping the user experience. > It's the same color as sockets right now, since that's unlikely to be > encountered during normal filename completion, but that could change.