Skip to content

Add PORTAGE_LOG_FILE_SEP option #1431

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Flowdalic
Copy link
Member

Portage uses the colon (:) as a separator between the components of a log file under PORTAGE_LOGDIR. However, the colon is often used as a "word" separator by shells and consoles, which makes it not user-friendly to select the full path of the log file. For example, double-clicking on a portage log file path in Kitty will not select the complete path, only the substring of the path up to the nearest colon.

Therefore, this introduces PORTAGE_LOG_FILE_SEP, which allows the user to choose the separator used for log files. To keep the existing behavior, PORTAGE_LOG_FILE_SEP defaults to ':'.

Portage uses the colon (:) as a separator between the components of a
log file under PORTAGE_LOGDIR. However, the colon is often used as a
"word" separator by shells and consoles, which makes it not
user-friendly to select the full path of the log file. For example,
double-clicking on a portage log file path in Kitty will not select
the complete path, only the substring of the path up to the nearest
colon.

Therefore, this introduces PORTAGE_LOG_FILE_SEP, which allows the user
to choose the separator used for log files. To keep the existing
behavior, PORTAGE_LOG_FILE_SEP defaults to ':'.

Signed-off-by: Florian Schmaus <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants