You are not logged in.

#1 2024-07-27 15:33:36

awptechnologies
Member
Registered: 2024-07-19
Posts: 67

.old files and .bak files show as a blank line

When running ls -a any files with the extension .old or .bak has the name hidden. I can see the line and file information but not a name. I can also nano into file. My question is what do i need to do to make all of these files visible when i run ls -a?

Offline

#2 2024-07-27 18:01:13

mpan
Member
Registered: 2012-08-01
Posts: 1,591
Website

Re: .old files and .bak files show as a blank line

Can you provide an example output? Put it inside [code][/code] tags.

Your current description is contradictory: you say you don’t see file name, but provide us with a part of that name (“.bak”, “.old”). You say you see “file information”, but `ls -a` doesn’t display anything besides names.

Also, please provide the output of running `type ls`.


Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!

Offline

#3 2024-07-27 18:44:15

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,314

Re: .old files and .bak files show as a blank line

This smells like dircolors
Does this show the filename:

ls -a --color=never

Offline

#4 2024-07-28 05:45:58

awptechnologies
Member
Registered: 2024-07-19
Posts: 67

Re: .old files and .bak files show as a blank line

ls -ll
total 32
-rw------- 1 alan alan  2602 Jul 13 01:51 id_rsa
-rwxr-x--- 1 alan alan   569 Jul 13 01:51 id_rsa.pub
-rw------- 1 alan alan 10866 Jul 25 02:11 known_hosts
-rw------- 1 alan alan 10126 Jul 25 02:11

This is how it shows but i know the file not listed is known_hosts.old

This happens all over the system. For instance when i make a copy of a config file and name it .bak

ls -a shows nothing about it

ls -a 
.  ..  id_rsa  id_rsa.pub  known_hosts

Last edited by awptechnologies (2024-07-28 22:20:37)

Offline

#5 2024-07-28 07:00:39

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,314

Re: .old files and .bak files show as a blank line

Please use [code][/code] tags.

Is that a manual transcription?

mpan wrote:

Also, please provide the output of running `type ls`.

seth wrote:

Does this show the filename:

ls -a --color=never

Offline

#6 2024-07-28 18:02:29

awptechnologies
Member
Registered: 2024-07-19
Posts: 67

Re: .old files and .bak files show as a blank line

Yes the ls -a --color=never worked? So whats my next move? i use zsh and i can list my .zshrc if need be.

Offline

#7 2024-07-28 18:12:50

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,314

Re: .old files and .bak files show as a blank line

Fix your dircolors, you've set those suffixes to the color of the background.
The text is printed, it's just like a white rabbit in the snow.

Offline

#8 2024-07-28 18:19:54

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: .old files and .bak files show as a blank line

I'd wager this could be a result of OMZ, which itself only makes any sense at all when you're chasing the white rabbit.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#9 2024-07-28 19:15:27

awptechnologies
Member
Registered: 2024-07-19
Posts: 67

Re: .old files and .bak files show as a blank line

Sounds good. i will look through my .zshrc file and try to change the color. I have used a tutorial to make my zsh look like kali here is my .zshrc what would control the colors of files with these types of extenstions?

]# ~/.zshrc file for zsh interactive shells.

# see /usr/share/doc/zsh/examples/zshrc for examples

setopt autocd # change directory just by typing its name

setopt correct # auto correct mistakes

setopt interactivecomments # allow comments in interactive mode

setopt magicequalsubst # enable filename expansion for arguments of the form ‘anything=expression’

setopt nonomatch # hide error message if there is no match for the pattern

setopt notify # report the status of background jobs immediately

setopt numericglobsort # sort filenames numerically when it makes sense

setopt promptsubst # enable command substitution in prompt


WORDCHARS=${WORDCHARS//\/} # Don't consider certain characters part of the word


# hide EOL sign ('%')

PROMPT_EOL_MARK=""

# configure key keybindings

bindkey -e # emacs key bindings

bindkey ' ' magic-space # do history expansion on space

bindkey '^U' backward-kill-line # ctrl + U

bindkey '^[[3;5~' kill-word # ctrl + Supr

bindkey '^[[3~' delete-char # delete

bindkey '^[[1;5C' forward-word # ctrl + ->

bindkey '^[[1;5D' backward-word # ctrl + <-

bindkey '^[[5~' beginning-of-buffer-or-history # page up

bindkey '^[[6~' end-of-buffer-or-history # page down

bindkey '^[[H' beginning-of-line # home

bindkey '^[[F' end-of-line # end

bindkey '^[[Z' undo # shift + tab undo last action

# enable completion features

autoload -Uz compinit

compinit -d ~/.cache/zcompdump

zstyle ':completion:*:*:*:*:*' menu select

zstyle ':completion:*' auto-description 'specify: %d'

zstyle ':completion:*' completer _expand _complete

zstyle ':completion:*' format 'Completing %d'

zstyle ':completion:*' group-name ''

zstyle ':completion:*' list-colors ''

zstyle ':completion:*' list-prompt %SAt %p: Hit TAB for more, or the character to insert%s

zstyle ':completion:*' matcher-list 'm:{a-zA-Z}={A-Za-z}'

zstyle ':completion:*' rehash true

zstyle ':completion:*' select-prompt %SScrolling active: current selection at %p%s

zstyle ':completion:*' use-compctl false

zstyle ':completion:*' verbose true

zstyle ':completion:*:kill:*' command 'ps -u $USER -o pid,%cpu,tty,cputime,cmd'

# History configurations

HISTFILE=~/.zsh_history

HISTSIZE=1000

SAVEHIST=2000

setopt hist_expire_dups_first # delete duplicates first when HISTFILE size exceeds HISTSIZE

setopt hist_ignore_dups # ignore duplicated commands history list

setopt hist_ignore_space # ignore commands that start with space

setopt hist_verify # show command with history expansion to user before running it

#setopt share_history # share command history data

# force zsh to show the complete history

alias history="history 0"


# configure `time` format

TIMEFMT=$'\nreal\t%E\nuser\t%U\nsys\t%S\ncpu\t%P'

# make less more friendly for non-text input files, see lesspipe(1)

#[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)

if [ -z "${arch_chroot:-}" ] && [ -r /etc/arch_chroot ]; then

arch_chroot=$(cat /etc/arch_chroot)

fi

# set a fancy prompt (non-color, unless we know we "want" color)

case "$TERM" in

xterm-color|*-256color) color_prompt=yes;;

esac
# uncomment for a colored prompt, if the terminal has the capability; turned

# off by default to not distract the user: the focus in a terminal window

# should be on the output of commands, not on the prompt

force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then

if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then

# We have color support; assume it's compliant with Ecma-48

# (ISO/IEC-6429). (Lack of such support is extremely rare, and such

# a case would tend to support setf rather than setaf.)

color_prompt=yes

else

color_prompt=

fi

fi

configure_prompt() {

prompt_symbol=㉿

# Skull emoji for root terminal

#[ "$EUID" -eq 0 ] && prompt_symbol=?

case "$PROMPT_ALTERNATIVE" in

twoline)

PROMPT=$'%F{%(#.blue.green)}┌──${arch_chroot:+($arch_chroot)─}${VIRTUAL_ENV:+($(basename $VIRTUAL_ENV))─}(%B%F{%(#.red.blue)}%n'$prompt_symbol$'%m%b%F{%(#.blue.green)})-[%B%F{reset}%(6~.%-1~/…/%4~.%5~)%b%F{%(#.blue.green)}]\n└─%B%(#.%F{red}#.%F{blue}$)%b%F{reset} '

# Right-side prompt with exit codes and background processes

#RPROMPT=$'%(?.. %? %F{red}%B⨯%b%F{reset})%(1j. %j %F{yellow}%B⚙%b%F{reset}.)'

;;

oneline)

PROMPT=$'${arch_chroot:+($arch_chroot)}${VIRTUAL_ENV:+($(basename $VIRTUAL_ENV))}%B%F{%(#.red.blue)}%n@%m%b%F{reset}:%B%F{%(#.blue.green)}%~%b%F{reset}%(#.#.$) '

RPROMPT=

;;

backtrack)

PROMPT=$'${arch_chroot:+($arch_chroot)}${VIRTUAL_ENV:+($(basename $VIRTUAL_ENV))}%B%F{red}%n@%m%b%F{reset}:%B%F{blue}%~%b%F{reset}%(#.#.$) '

RPROMPT=

;;

esac

unset prompt_symbol

}

# The following block is surrounded by two delimiters.

# These delimiters must not be modified. Thanks.

# START KALI CONFIG VARIABLES

PROMPT_ALTERNATIVE=twoline

NEWLINE_BEFORE_PROMPT=yes

# STOP KALI CONFIG VARIABLES

if [ "$color_prompt" = yes ]; then

# override default virtualenv indicator in prompt

VIRTUAL_ENV_DISABLE_PROMPT=1

configure_prompt

# enable syntax-highlighting

if [ -f /usr/share/zsh/plugins/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh ]; then

. /usr/share/zsh/plugins/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh

ZSH_HIGHLIGHT_HIGHLIGHTERS=(main brackets pattern)

ZSH_HIGHLIGHT_STYLES[default]=none

ZSH_HIGHLIGHT_STYLES[unknown-token]=fg=white,underline

ZSH_HIGHLIGHT_STYLES[reserved-word]=fg=cyan,bold

ZSH_HIGHLIGHT_STYLES[suffix-alias]=fg=green,underline

ZSH_HIGHLIGHT_STYLES[global-alias]=fg=green,bold

ZSH_HIGHLIGHT_STYLES[precommand]=fg=green,underline

ZSH_HIGHLIGHT_STYLES[commandseparator]=fg=blue,bold

ZSH_HIGHLIGHT_STYLES[autodirectory]=fg=green,underline

ZSH_HIGHLIGHT_STYLES[path]=bold

ZSH_HIGHLIGHT_STYLES[path_pathseparator]=

ZSH_HIGHLIGHT_STYLES[path_prefix_pathseparator]=

ZSH_HIGHLIGHT_STYLES[globbing]=fg=blue,bold

ZSH_HIGHLIGHT_STYLES[history-expansion]=fg=blue,bold

ZSH_HIGHLIGHT_STYLES[command-substitution]=none

ZSH_HIGHLIGHT_STYLES[command-substitution-delimiter]=fg=magenta,bold

ZSH_HIGHLIGHT_STYLES[process-substitution]=none

ZSH_HIGHLIGHT_STYLES[process-substitution-delimiter]=fg=magenta,bold

ZSH_HIGHLIGHT_STYLES[single-hyphen-option]=fg=green

ZSH_HIGHLIGHT_STYLES[double-hyphen-option]=fg=green

ZSH_HIGHLIGHT_STYLES[back-quoted-argument]=none

ZSH_HIGHLIGHT_STYLES[back-quoted-argument-delimiter]=fg=blue,bold

ZSH_HIGHLIGHT_STYLES[single-quoted-argument]=fg=yellow

ZSH_HIGHLIGHT_STYLES[double-quoted-argument]=fg=yellow

ZSH_HIGHLIGHT_STYLES[dollar-quoted-argument]=fg=yellow

ZSH_HIGHLIGHT_STYLES[rc-quote]=fg=magenta

ZSH_HIGHLIGHT_STYLES[dollar-double-quoted-argument]=fg=magenta,bold

ZSH_HIGHLIGHT_STYLES[back-double-quoted-argument]=fg=magenta,bold

ZSH_HIGHLIGHT_STYLES[back-dollar-quoted-argument]=fg=magenta,bold

ZSH_HIGHLIGHT_STYLES[assign]=none

ZSH_HIGHLIGHT_STYLES[redirection]=fg=blue,bold

ZSH_HIGHLIGHT_STYLES[comment]=fg=black,bold

ZSH_HIGHLIGHT_STYLES[named-fd]=none

ZSH_HIGHLIGHT_STYLES[numeric-fd]=none

ZSH_HIGHLIGHT_STYLES[arg0]=fg=cyan

ZSH_HIGHLIGHT_STYLES[bracket-error]=fg=red,bold

ZSH_HIGHLIGHT_STYLES[bracket-level-1]=fg=blue,bold

ZSH_HIGHLIGHT_STYLES[bracket-level-2]=fg=green,bold

ZSH_HIGHLIGHT_STYLES[bracket-level-3]=fg=magenta,bold

ZSH_HIGHLIGHT_STYLES[bracket-level-4]=fg=yellow,bold

ZSH_HIGHLIGHT_STYLES[bracket-level-5]=fg=cyan,bold

ZSH_HIGHLIGHT_STYLES[cursor-matchingbracket]=standout

fi

else

PROMPT='${arch_chroot:+($arch_chroot)}%n@%m:%~%(#.#.$) '

fi

unset color_prompt force_color_prompt


toggle_oneline_prompt(){

if [ "$PROMPT_ALTERNATIVE" = oneline ]; then

PROMPT_ALTERNATIVE=twoline

else

PROMPT_ALTERNATIVE=oneline

fi

configure_prompt

zle reset-prompt

}

zle -N toggle_oneline_prompt

bindkey ^P toggle_oneline_prompt


# If this is an xterm set the title to user@host:dir

case "$TERM" in

xterm*|rxvt*|Eterm|aterm|kterm|gnome*|alacritty)

TERM_TITLE=$'\e]0;${arch_chroot:+($arch_chroot)}${VIRTUAL_ENV:+($(basename $VIRTUAL_ENV))}%n@%m: %~\a'

;;

*)

;;

esac

precmd() {

# Print the previously configured title

print -Pnr -- "$TERM_TITLE"

# Print a new line before the prompt, but only if it is not the first line

if [ "$NEWLINE_BEFORE_PROMPT" = yes ]; then

if [ -z "$_NEW_LINE_BEFORE_PROMPT" ]; then

_NEW_LINE_BEFORE_PROMPT=1

else

print ""

fi

fi

}


# enable color support of ls, less and man, and also add handy aliases

if [ -x /usr/bin/dircolors ]; then

test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"

export LS_COLORS="$LS_COLORS:ow=30;44:" # fix ls color for folders with 777 permissions


alias ls='ls --color=auto'

#alias dir='dir --color=auto'

#alias vdir='vdir --color=auto'

alias grep='grep --color=auto'

alias fgrep='fgrep --color=auto'

alias egrep='egrep --color=auto'

alias diff='diff --color=auto'

alias ip='ip --color=auto'

export LESS_TERMCAP_mb=$'\E[1;31m' # begin blink

export LESS_TERMCAP_md=$'\E[1;36m' # begin bold

export LESS_TERMCAP_me=$'\E[0m' # reset bold/blink

export LESS_TERMCAP_so=$'\E[01;33m' # begin reverse video

export LESS_TERMCAP_se=$'\E[0m' # reset reverse video

export LESS_TERMCAP_us=$'\E[1;32m' # begin underline

export LESS_TERMCAP_ue=$'\E[0m' # reset underline

# Take advantage of $LS_COLORS for completion as well

zstyle ':completion:*' list-colors "${(s.:.)LS_COLORS}"

zstyle ':completion:*:*:kill:*:processes' list-colors '=(#b) #([0-9]#)*=0=01;31'

fi

# some more ls aliases

alias ll='ls -l'

alias la='ls -A'

alias l='ls -CF'

# enable auto-suggestions based on the history

if [ -f /usr/share/zsh/plugins/zsh-autosuggestions/zsh-autosuggestions.zsh ]; then

. /usr/share/zsh/plugins/zsh-autosuggestions/zsh-autosuggestions.zsh

# change suggestion color

ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE='fg=#999'

fi


# enable command-not-found if installed

if [ -f /etc/zsh_command_not_found ]; then

. /etc/zsh_command_not_found

fi

compinit 

Last edited by awptechnologies (2024-07-28 22:19:06)

Offline

#10 2024-07-28 19:28:36

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,314

Re: .old files and .bak files show as a blank line

The problem is in ~/.dircolors and please use [code][/code] tags. Edit your post in this regard.

Offline

#11 2024-07-28 19:48:19

awptechnologies
Member
Registered: 2024-07-19
Posts: 67

Re: .old files and .bak files show as a blank line

Im new to the arch form and i really appreciate your help. Im trying to figure out what you mean but code tags

do i need to learn from the how to upload text link?

Offline

#12 2024-07-28 20:11:44

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,314

Re: .old files and .bak files show as a blank line

The comment bot explains the code tags and links https://bbs.archlinux.org/help.php#bbcode
You don't really need to post your zshrc at all, fix the colors in ~/.dircolors and you should be good.

Offline

#13 2024-07-28 20:18:22

awptechnologies
Member
Registered: 2024-07-19
Posts: 67

Re: .old files and .bak files show as a blank line

i dont have that directory...

Offline

#14 2024-07-28 20:32:57

awptechnologies
Member
Registered: 2024-07-19
Posts: 67

Re: .old files and .bak files show as a blank line

i use gnome-terminal so i changed the color profile and i can see them. What window manager or application would create that directory? i use gnome in all of my linux installs and have never seen that directory.

Offline

#15 2024-07-28 20:34:44

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,314

Re: .old files and .bak files show as a blank line

Fix the code tags if you want to continue this.

You're trying to load it

if [ -x /usr/bin/dircolors ]; then

test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"

export LS_COLORS="$LS_COLORS:ow=30;44:" # fix ls color for folders with 777 permissions

Post the output of

echo $LS_COLORS

*in code tags!*

Edit:

i use gnome-terminal so i changed the color profile and i can see them

And what color profile was that? The default one?

The default dircolors default bak to 90 (dark gray), so if your background is the same as the color schemes dark gray, you get a gray owl at dusk.
gnome-terminal also supports 256 colors, read the wiki on how to customize your dircolors.

Here's a script to print all color combinations:

#!/bin/sh

if [ "$1" = "256" ]; then
    for fgbg in 38 48 ; do # Foreground / Background
        echo "\\e[${fgbg};5;<number>m"
        for color in {0..255} ; do # Colors
            # Display the color
            printf "\e[${fgbg};5;%sm  %3s  \e[0m" $color $color
            # Display 16 colors per lines
            if [ $((($color + 1) % 16)) == 0 ] ; then
                echo # New line
            fi
        done
        echo # New line
    done
else
    for x in 0 1 4 5 7 8; do
        for i in {30..37}; do
            for a in {40..47}; do
                printf "\e[$x;$i;$a""m\\\e[$x;$i;$a""m\e[0m "
            done
            echo
        done
    done
    echo
fi%     

Last edited by seth (2024-07-28 20:45:52)

Offline

#16 2024-07-28 22:19:24

awptechnologies
Member
Registered: 2024-07-19
Posts: 67

Re: .old files and .bak files show as a blank line

did i do the code tags right?

Offline

#17 2024-07-28 22:22:37

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,612

Re: .old files and .bak files show as a blank line

awptechnologies wrote:

did i do the code tags right?

Perfect.  Thank you


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

Board footer

Powered by FluxBB