summaryrefslogtreecommitdiff
path: root/doom
diff options
context:
space:
mode:
authorZofia Szweda <sophies@disroot.org>2026-09-15 19:22:16 +0200
committerZofia Szweda <sophies@disroot.org>2026-09-15 19:22:16 +0200
commit8e5a2e3d02fe21a4674c001b7b1790154055d2c7 (patch)
tree0f793a43d957879d23294d99051043e54e03f2e4 /doom
parent0c767e6611176f36ecbae4e39cbff3d9e1599746 (diff)
emacs: remove a lot of unnecessary comments in config files
Diffstat (limited to 'doom')
-rw-r--r--doom/.config/doom/config.el44
-rw-r--r--doom/.config/doom/init.el14
-rw-r--r--doom/.config/doom/packages.el52
3 files changed, 0 insertions, 110 deletions
diff --git a/doom/.config/doom/config.el b/doom/.config/doom/config.el
index 40637ef..a176fc9 100644
--- a/doom/.config/doom/config.el
+++ b/doom/.config/doom/config.el
@@ -1,53 +1,9 @@
;;; $DOOMDIR/config.el -*- lexical-binding: t; -*-
(remove-hook 'doom-first-input-hook #'evil-snipe-mode)
-;; Place your private configuration here! Remember, you do not need to run 'doom
-;; sync' after modifying this file!
-
-
-;; Some functionality uses this to identify you, e.g. GPG configuration, email
-;; clients, file templates and snippets. It is optional.
-;; (setq user-full-name "John Doe"
-;; user-mail-address "john@doe.com")
-
-;; Doom exposes five (optional) variables for controlling fonts in Doom:
-;;
-;; - `doom-font' -- the primary font to use
-;; - `doom-variable-pitch-font' -- a non-monospace font (where applicable)
-;; - `doom-big-font' -- used for `doom-big-font-mode'; use this for
-;; presentations or streaming.
-;; - `doom-symbol-font' -- for symbols
-;; - `doom-serif-font' -- for the `fixed-pitch-serif' face
-;;
-;; See 'C-h v doom-font' for documentation and more examples of what they
-;; accept. For example:
-;;
-;;
(setq doom-font (font-spec :family "Berkeley Mono" :size 12.0))
-;; If you or Emacs can't find your font, use 'M-x describe-font' to look them
-;; up, `M-x eval-region' to execute elisp code, and 'M-x doom/reload-font' to
-;; refresh your font settings. If Emacs still can't find your font, it likely
-;; wasn't installed correctly. Font issues are rarely Doom issues!
-
-;; There are two ways to load a theme. Both assume the theme is installed and
-;; available. You can either set `doom-theme' or manually load a theme with the
-;; `load-theme' function. This is the default:
(setq doom-theme 'doom-badger)
-;; Specify both a dark and light theme, like so and Doom will choose which one
-;; to load based on your system light/dark setting:
-;;
-;; (setq doom-theme '(doom-one . doom-one-light)) ; (DARK . LIGHT)
-;;
-;; If you want more pro-active theme switching based on OS light/dark mode, look
-;; up the `auto-dark' package.
-
-;; This determines the style of line numbers in effect. If set to `nil', line
-;; numbers are disabled. For relative line numbers, set this to `relative'.
(setq display-line-numbers-type t)
-
-;; If you use `org' and don't want your org files in the default location below,
-;; change `org-directory'. It must be set before org loads!
(setq org-directory "~/notes/")
-;; commented for now
(use-package! emms
:config
(require 'emms-setup)
diff --git a/doom/.config/doom/init.el b/doom/.config/doom/init.el
index 77a4aa8..e3776cc 100644
--- a/doom/.config/doom/init.el
+++ b/doom/.config/doom/init.el
@@ -1,19 +1,5 @@
;;; $DOOMDIR/init.el -*- lexical-binding: t; -*-
-;; This file controls what Doom modules are enabled and what order they load
-;; in. Remember to run 'doom sync' after modifying it!
-
-;; NOTE: Press 'SPC h d h' (or 'C-h d h' for non-vim users) to access Doom's
-;; documentation. There you'll find a link to Doom's Module Index where all of
-;; our modules are listed, including what flags they support.
-
-;; NOTE: Move your cursor over a module's name (or its flags) and press 'K' (or
-;; 'C-c c k' for non-vim users) to view its documentation. This works on flags
-;; as well (those symbols that start with a plus).
-;;
-;; Alternatively, press 'gd' (or 'C-c c d') on a module to browse its
-;; directory (for easy access to its source code).
-
(doom! :input
;;bidi ; (tfel ot) thgir etirw uoy gnipleh
;;chinese
diff --git a/doom/.config/doom/packages.el b/doom/.config/doom/packages.el
index 6d948aa..9e2457e 100644
--- a/doom/.config/doom/packages.el
+++ b/doom/.config/doom/packages.el
@@ -1,56 +1,4 @@
;;; $DOOMDIR/packages.el -*- lexical-binding: t; no-byte-compile: t -*-
-
-;; To install a package:
-;;
-;; 1. Declare them here in a `package!' statement,
-;; 2. Run 'doom sync' in the shell,
-;; 3. Restart Emacs.
-;;
-;; Use 'C-h f package\!' to look up documentation for the `package!' macro.
-
-
-;; To install SOME-PACKAGE from MELPA, ELPA or emacsmirror:
-;; (package! some-package)
-
-;; To install a package directly from a remote git repo, you must specify a
-;; `:recipe'. You'll find documentation on what `:recipe' accepts here:
-;; https://github.com/radian-software/straight.el#the-recipe-format
-;; (package! another-package
-;; :recipe (:host github :repo "username/repo"))
-
-;; If the package you are trying to install does not contain a PACKAGENAME.el
-;; file, or is located in a subdirectory of the repo, you'll need to specify
-;; `:files' in the `:recipe':
-;; (package! this-package
-;; :recipe (:host github :repo "username/repo"
-;; :files ("some-file.el" "src/lisp/*.el")))
-
-;; If you'd like to disable a package included with Doom, you can do so here
-;; with the `:disable' property:
-;; (package! builtin-package :disable t)
-
-;; You can override the recipe of a built in package without having to specify
-;; all the properties for `:recipe'. These will inherit the rest of its recipe
-;; from Doom or MELPA/ELPA/Emacsmirror:
-;; (package! builtin-package :recipe (:nonrecursive t))
-;; (package! builtin-package-2 :recipe (:repo "myfork/package"))
-
-;; Specify a `:branch' to install a package from a particular branch or tag.
-;; This is required for some packages whose default branch isn't 'master' (which
-;; our package manager can't deal with; see radian-software/straight.el#279)
-;; (package! builtin-package :recipe (:branch "develop"))
-
-;; Use `:pin' to specify a particular commit to install.
-;; (package! builtin-package :pin "1a2b3c4d5e")
-
-
-;; Doom's packages are pinned to a specific commit and updated from release to
-;; release. The `unpin!' macro allows you to unpin single packages...
-;; (unpin! pinned-package)
-;; ...or multiple packages
-;; (unpin! pinned-package another-pinned-package)
-;; ...Or *all* packages (NOT RECOMMENDED; will likely break things)
-;; (unpin! t)
(package! jabber)
(package! mood-line)
(package! tomlparse