Bug 235928

Summary: xemacs tabify/untabify not working
Product: [Fedora] Fedora Reporter: Tim Taiwanese Liim <tim.liim>
Component: xemacsAssignee: Ville Skyttä <ville.skytta>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-04-11 11:07:08 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Tim Taiwanese Liim 2007-04-10 16:40:43 EDT
Description of problem:
    The tabify/untabify command disappears in FC6.  It was available 
    in FC5 (xemacs 21.4 (patch 19)).

Version-Release number of selected component (if applicable):
    xemacs-packages-base-20060510-3.fc6
    xemacs-21.5.27-8.fc6
    xemacs-common-21.5.27-8.fc6
    XEmacs 21.5  (beta27) "fiddleheads" (linux, Mule) of Thu Jan 25 2007 on hammer2
    [version 21.5.27 of May 2006]

How reproducible:
    always

Steps to Reproduce:
    1. start xemacs
    2. M-x tabify
  
Actual results:
    - tabify unrecognized.  Same for untabify.

Expected results:
    - command tabify should be available.

Additional info:
Comment 1 Tim Taiwanese Liim 2007-04-10 22:53:42 EDT
Some other commands that are missing since FC5:
    display-time
    vc-load-vc-hooks
Maybe they are missing for a good reason that I don't understand.
Comment 2 Jens Petersen 2007-04-10 23:20:50 EDT
I suspect you're missing some xemacs-sumo packages since they're not
all installed by default any more.
Comment 3 Ville Skyttä 2007-04-11 11:07:08 EDT
Right, install the xemacs-packages-extra package.  It's regrettable that during
the FC5->FC6 upgrade, xemacs-packages-extra was not pulled in for people who had
xemacs-sumo installed.
Comment 4 Tim Taiwanese Liim 2007-04-11 11:28:54 EDT
Thanks!  Yes xemacs-packages-extra solved the issue.  Yes it's
rather hard for users to guess which xemacs-related rpms to pull in.