Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bashdb evaluates escape codes when it's printing the current line of source code

Open
  • Is something wrong?
#32 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
bash
Domain
devtools

Research direction

Reproduce the example script and trace where bashdb prints the current source line, checking lib/hooks.sh as suggested in the issue. The fix is complete when escape sequences in a line such as RED=$'\x1b[31m' are displayed unchanged rather than evaluated.

Written by the indexing model from the issue text.

Description

Debugging the snippet yields this (in red color):

(/home/jansorg/test.bash:2):
2:      RED=$''
bashdb<0>

But it should have printed the source line unchanged, i.e. as RED=$'\x1b[31m'.

I tried to fix this, but couldn't find the place where the source line is printed (in lib/hooks.sh?).
If you pointed me to the right source, I'd try again to fix this.

#!/bin/bash
RED=$'\x1b[31m'
RESET=$'\x1b[0m'

read -e -p "Please enter a name: " -r NAME
echo "The name is $RED$NAME$RESET!"
Dominant language
Shell
Stars
98
Forks
13
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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 Trepan-Debuggers/bashdb

All issues in Trepan-Debuggers/bashdb

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.