如何在bash与csh中自定义~/.history文件格式？

Let me break this down clearly based on how each shell handles history storage and customization:

csh/tcsh: Navigating the Default .history Format #

First, the ~/.history format you’re seeing (like #+1475165422 exit) is hardwired into csh/tcsh—it’s the shell’s native way of storing command history for efficient reading and parsing. The #+<timestamp> prefix is a Unix epoch timestamp, which the shell translates to a human-readable time when you run the history command.

Can you customize this storage format? #

Short answer: Not easily, and it’s not recommended. The shell depends on this exact structure to load your command history correctly. If you manually modify the file’s format, csh/tcsh may fail to parse your history entirely.

That said, you can customize how history is displayed (which you already know for tcsh):

set history = ( 10 "%T %R" )

This controls what the history command outputs (in this case, showing the time %T and raw command %R), but it doesn’t alter the underlying storage format in ~/.history.

bash: Tailoring History Storage and Display #

Bash operates similarly, but with a few key differences for its default history file (~/.bash_history):

Default vs. Timestamped Storage #

By default, bash only stores raw commands in ~/.bash_history. When you set export HISTTIMEFORMAT="%T", bash starts prepending each command with a #<timestamp> line (e.g., #1620000000\nls -al) to track command timestamps. This format is also built into bash for reliable history parsing.

Customizing Display vs. Storage #

• To tweak how history is displayed, keep using HISTTIMEFORMAT—you can adjust the format string (e.g., "%Y-%m-%d %T " for full date and time).
• If you want a custom storage format (more human-readable than the default timestamped lines), don’t modify ~/.bash_history directly. Instead, use PROMPT_COMMAND to write to a separate custom history file. Add this to your ~/.bashrc:

PROMPT_COMMAND='{ date "+%Y-%m-%d %T" && history 1; } >> ~/.custom_history'

This appends each command (with a readable timestamp) to ~/.custom_history every time you run a command, while leaving ~/.bash_history intact for bash’s native history functionality.

Key Takeaway #

Both shells use built-in history file formats to ensure reliable loading of your command history. Modifying these default files is risky and likely to break history features. Instead:

• Use shell-specific variables to adjust how history is displayed.
• For custom storage, create a separate log file using scripts or shell hooks like PROMPT_COMMAND (bash) or precmd (tcsh) to avoid disrupting the shell’s native history system.

内容的提问来源于stack exchange，提问作者user1102185