How to Install and Uninstall emacs-company-mode.noarch Package on Fedora 39
Last updated: January 18,2025
1. Install "emacs-company-mode.noarch" package
Please follow the guidance below to install emacs-company-mode.noarch on Fedora 39
$
sudo dnf update
Copied
$
sudo dnf install
emacs-company-mode.noarch
Copied
2. Uninstall "emacs-company-mode.noarch" package
Please follow the guidelines below to uninstall emacs-company-mode.noarch on Fedora 39:
$
sudo dnf remove
emacs-company-mode.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the emacs-company-mode.noarch package on Fedora 39
Last metadata expiration check: 0:59:10 ago on Thu Mar 7 11:44:58 2024.
Available Packages
Name : emacs-company-mode
Version : 0.10.1
Release : 1.fc39
Architecture : noarch
Size : 142 k
Source : emacs-company-mode-0.10.1-1.fc39.src.rpm
Repository : updates
Summary : Modular in-buffer completion framework for Emacs
URL : https://company-mode.github.io/
License : GPL-3.0-or-later
Description : Company is a text completion framework for Emacs. The name stands for
: "complete anything". It uses pluggable back-ends and front-ends to
: retrieve and display completion candidates. It comes with several
: back-ends such as Elisp, Clang, Semantic, Eclim, Ropemacs, Ispell, CMake,
: BBDB, Yasnippet, dabbrev, etags, gtags, files, keywords and a few others.
:
: The CAPF back-end provides a bridge to the standard
: completion-at-point-functions facility, and thus works with any major
: mode that defines a proper completion function.
Available Packages
Name : emacs-company-mode
Version : 0.10.1
Release : 1.fc39
Architecture : noarch
Size : 142 k
Source : emacs-company-mode-0.10.1-1.fc39.src.rpm
Repository : updates
Summary : Modular in-buffer completion framework for Emacs
URL : https://company-mode.github.io/
License : GPL-3.0-or-later
Description : Company is a text completion framework for Emacs. The name stands for
: "complete anything". It uses pluggable back-ends and front-ends to
: retrieve and display completion candidates. It comes with several
: back-ends such as Elisp, Clang, Semantic, Eclim, Ropemacs, Ispell, CMake,
: BBDB, Yasnippet, dabbrev, etags, gtags, files, keywords and a few others.
:
: The CAPF back-end provides a bridge to the standard
: completion-at-point-functions facility, and thus works with any major
: mode that defines a proper completion function.