Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1925181 - internal_vim_alias mechanism makes bash jobs commmand useless
Summary: internal_vim_alias mechanism makes bash jobs commmand useless
Keywords:
Status: CLOSED DUPLICATE of bug 1918575
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 33
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Karsten
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-04 14:37 UTC by Mats Wichmann
Modified: 2021-02-05 05:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-05 05:08:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Mats Wichmann 2021-02-04 14:37:47 UTC 
Description of problem:


Version-Release number of selected component (if applicable): vim-enhanced 8.2.2146-2


How reproducible: always


Steps to Reproduce:
Edit a file with vi (or vim). 
Put in background with ^Z. 
Run "jobs"


Actual results:
[1]-  Stopped                 ( test -f /usr/bin/vim && exec /usr/bin/vim "$@"; test -f /usr/bin/vi && exec /usr/bin/vi "$@" )
[2]+  Stopped                 ( test -f /usr/bin/vim && exec /usr/bin/vim "$@"; test -f /usr/bin/vi && exec /usr/bin/vi "$@" )


Expected results: something like:
[1]+  Stopped                 vi /etc/profile.d/vim.sh
[2]+  Stopped                 vi /etc/issue


Additional info: the fancy machinery here completely obscures the ability to see the file being edited if the editor has been job-control stopped.
Comment 1 Zdenek Dohnal 2021-02-05 05:08:47 UTC 
Hi Mats,

thanks for reporting the issue!

The fix for this already came into testing repo yesterday, so I'm closing this as a duplicate.

*** This bug has been marked as a duplicate of bug 1918575 ***
Note You need to log in before you can comment on or make changes to this bug.