Bug 1918348

Summary: Shell alias for vim gives meaningless job control names
Product: [Fedora] Fedora Reporter: Paul Boddie <paul.boddie>
Component: vimAssignee: Karsten <karsten>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: gchamoul, karsten, zdohnal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-21 05:33:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paul Boddie 2021-01-20 14:08:28 UTC 
Description of problem:

When invoking vim or vi in bash, the jobs that are shown when using the jobs command all have meaningless (or uninformative) names. They all appear like this:

( test -f /usr/bin/vim && exec /usr/bin/vim "$@"; test -f /usr/bin/vi && exec /usr/bin/vi "$@" )

Instead, I would expect them to appear like this:

vim filename.txt

Version-Release number of selected component (if applicable):

vim-enhanced-8.2.2146-2.fc33.x86_64

How reproducible:

Very.

Steps to Reproduce:
1. Open a shell.
2. Start vi or vim from the shell command line.
3. Ctrl-Z to suspend vim.
4. Invoke jobs.

Actual results:

( test -f /usr/bin/vim && exec /usr/bin/vim "$@"; test -f /usr/bin/vi && exec /usr/bin/vi "$@" )

Expected results:

vim filename.txt

Additional info:

I didn't notice this in Fedora 32, so I suspect it is a regression.
Comment 1 Zdenek Dohnal 2021-01-21 05:33:42 UTC 
Hi Paul,

thank you for reporting the issue!

Actually what you discovered is the same as Glenn found here https://bugzilla.redhat.com/show_bug.cgi?id=1907800#c14 . The reason of this is the function called as aliases is called in subshell.

The current aliases solution have more problems, so I will try to use alternatives to do the trick - I created a separate bug for it (https://bugzilla.redhat.com/show_bug.cgi?id=1918575) and I'll close this bug as its duplicate.

*** This bug has been marked as a duplicate of bug 1918575 ***