open folders are in dark blu over black

Open
#585 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
linux
Domain
desktop

Research direction

Start by reproducing the Nemo terminal-plugin prompt-color problem with the reported black background and Tango profile palette. Compare its folder-path rendering with the user's normal Terminal settings; done means the folder path is readable and matches the normal Terminal colors.

Written by the indexing model from the issue text.

Description

Hi
I started to use this Terminal-plugin within Nemo (at top) and unfortunately I have the green prompt - i.e. user@user: as set, but any folder I one it is in dark blue over a black background - impossible to read.

user@user: /Documents$ - user@user is GREEN as set and : is light-grey, **/Documents** is dark blue, $ is light-grey

I see there is no way to adjust colours (UK) as in the actual Terminal.

In my 'normal' Terminal window is:

user@user is green as set - : is light-grey
~/Documents is Light-Blue and visible - $ is light-grey

All in Black background and readable.

This is the only problem I have.

I am no Linux expert, but a veteran Windows user moved to Linux about 1.5-2 years ago.

Id it fixable?

I saw somewhere, someone did a little mod, bu tI had no idea how to make it work, but I do not understand why it does not automatically set it as Terminal is set by user = easier!

Thanks
M

PS all I ask is to mime exactly as the normal Terminal windows is set - if possible

I believe mine is set as Profile Palette Tango and variations

Dominant language
C
Stars
486
Forks
172
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/nemo-extensions

All issues in linuxmint/nemo-extensions

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.