Sesson log filename incorrect
Bug report
- iTerm2 version: 3.4.16
- OS version: macOS Monterey 12.5
Detailed steps to reproduce the problem
- Open a new session; the session type is irrelevant (i.e. SSH, shell)
- Perform 5 or so commands.
- Exit the session.
- Check the filename of the session log for the session just closed.
- Note that the filename does not conform to the syntax defined in the
com.googlecode.iterm2.plist
file (see below).
Background
- It appears that the session log filename syntax is defined in
com.googlecode.iterm2.plist
with the following statement:<string>\(session.name)-\(session.creationTimeString)_\(iterm2.pid).log</string>
- As an example, the log for a session to toolsServer1 that was opened on 08/12/2022 @ 5:00.25pm might have the following filename:
toolServer1-20220812_170025_1018.log
- This did work in v3.1.5.
- The same exact same syntax statement is seen in the
com.googlecode.iterm2.plist
files for both iTerm2 versions:- v3.1.5 = works
- v3.4.16 = fails
What happened
- The session log filename is missing the session name. So the actual filename is as follows:
-20220812_170025_1018.log