gemini-cli - 💡(How to fix) Fix Bug: shell history merges commands ending in a backslash [1 pull requests]

What happened?

Shell history corrupts any command that ends in a backslash. For example, after running dir C:\ and then ls, the history file contains two separate lines:

dir C:\
ls

On reload, readHistoryFile treats the trailing backslash as a line-continuation marker and returns one mangled entry, dir C: ls, instead of preserving the two commands.

What did you expect to happen?

History should reload exactly as writeHistoryFile stores it: one command per non-empty line. A real command that legitimately ends in a backslash should not be merged with the next history entry.

Root cause

writeHistoryFile stores commands verbatim with history.join('\n'), but readHistoryFile has legacy decoding logic that merges any stored line ending in an odd number of backslashes into the following line.

Because the writer never produces that escaped continuation format, the merge path only corrupts real commands that happen to end with a backslash.

Proposed fix

Read each non-empty history line as exactly one command, matching the writer. Add a regression test for a command ending in a backslash followed by another command.

Related PR: #27555