Bug 545791 - Emacs save-buffer command fails to save files when “break-hardlink-on-save” is set
Summary: Emacs save-buffer command fails to save files when “break-hardlink-on-save” i...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Petr Hracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-09 11:42 UTC by Robert Ransom
Modified: 2013-03-06 07:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-06 07:59:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robert Ransom 2009-12-09 11:42:38 UTC
Description of problem:
When the “break-hardlink-on-save” customization variable is set to T, I am unable to make Emacs save any file with C-x C-s, C-x C-w, or M-x save-buffer.  Emacs displays the following message in the minibuffer:

Wrong type argument: number-or-marker-p, nil


Version-Release number of selected component (if applicable):
emacs-23.1-13.fc12.x86_64

How reproducible:
always

Steps to Reproduce:
1. Start an emacs process and switch to a text buffer (*scratch* will work)
2. M-x customize-set-variable RET break-hardlink-on-save RET y
3. C-x C-w new-file-name.txt RET
  
Actual results:
The minibuffer shows “Wrong type argument: number-or-marker-p, nil”; the file is not saved.

In *Messages*, the message is prefixed with “basic-save-buffer-1: ”.

The error occurs both when trying to create a file and when trying to overwrite an existing non-hard-linked file; I have not tested overwriting a hard-linked file.


Expected results:
The file is saved.


Additional info:
Workaround: Disable “break-hardlink-on-save”:
M-x customize-save-variable RET break-hardlink-on-save RET n

Non-interactive saves still work -- the Emacs customize system can still save .emacs.

Comment 1 Bug Zapper 2010-11-04 03:50:33 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Robert Ransom 2010-11-04 12:38:51 UTC
This bug is still present in Emacs 23.2 as packaged by Arch Linux.

Comment 3 Fedora Admin XMLRPC Client 2013-02-27 15:47:16 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Petr Hracek 2013-03-06 07:59:06 UTC
That bug is solved since emacs 24.0.50
http://lists.gnu.org/archive/html/emacs-devel/2011-05/msg00476.html

In rawhide we have emacs-24.2
Correction is already in rawhide


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