Bug 864482 - /etc/virc does not know about /run/media
/etc/virc does not know about /run/media
Product: Fedora
Classification: Fedora
Component: vim (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Karsten Hopp
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-10-09 08:51 EDT by Bryn M. Reeves
Modified: 2013-07-31 22:07 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 22:07:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bryn M. Reeves 2012-10-09 08:51:07 EDT
Description of problem:
The standard /etc/virc uses an autocmd in the fedora augroup to disable writing swap files by default to paths commonly used for removable media and network file systems:

 25   " don't write swapfile on most commonly used directories for NFS mounts or USB sticks
 26   autocmd BufNewFile,BufReadPre /media/*,/mnt/* set directory=~/tmp,/var/tmp,/tmp

This should probably be extended to also filter /run/media since this is the new default location for removable media mounted in a user session.

Something like:

autocmd BufNewFile,BufReadPre /media/*,/mnt/*,/run/media/* set directory=~/tmp,/var/tmp,/tmp

Version-Release number of selected component (if applicable):
vim-minimal-7.3.* on F17 and greater

How reproducible:

Steps to Reproduce:
1. Edit a file on external media mounted under /run/media
2. Check for a swapfile
Actual results:
Swapfiles are created on external media mounted under /run

Expected results:
Swapfile behaviour consistent with traditional removable media mount paths

Additional info:
Comment 1 Fedora End Of Life 2013-07-03 19:26:08 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Fedora End Of Life 2013-07-31 22:07:32 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.