Added my information to my config

3 files changed, 75 insertions, 55 deletions

diff --git a/.doom.d/config.el b/.doom.d/config.el
index 3f4d1b65..494f8766 100644
--- a/.doom.d/config.el
+++ b/.doom.d/config.el
@@ -1,3 +1,9 @@
+;;
+;;  | '__/ _ \ / _` / __|    Roger González
+;;  | | | (_) | (_| \__ \    https://rogs.me
+;;  |_|  \___/ \__, |___/    https://git.rogs.me
+;;             |___/
+;;
 ;;; $DOOMDIR/config.el -*- lexical-binding: t; -*-
 
 ;; Place your private configuration here! Remember, you do not need to run 'doom
@@ -9,51 +15,51 @@
 (setq user-full-name "Roger Gonzalez"
       user-mail-address "roger@rogs.me")
 
-;; Doom exposes five (optional) variables for controlling fonts in Doom. Here
-;; are the three important ones:
-;;
-;; + `doom-font'
-;; + `doom-variable-pitch-font'
-;; + `doom-big-font' -- used for `doom-big-font-mode'
-;;
-;; They all accept either a font-spec, font string ("Input Mono-12"), or xlfd
-;; font string. You generally only need these two:
-;; test
-  (setq doom-font (font-spec :family "monospace" :size 28)
-      doom-variable-pitch-font (font-spec :family "sans"))
-
-;; 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. These are the defaults.
-(setq doom-theme 'doom-one)
-
-;; If you intend to use org, it is recommended you change this!
-  (setq org-directory "~/org")
-
-;; If you want to change the style of line numbers, change this to `relative' or
-;; `nil' to disable it:
-(setq display-line-numbers-type t)
-
-
-;; Here are some additional functions/macros that could help you configure Doom:
-;;
-;; - `load!' for loading external *.el files relative to this one
-;; - `use-package' for configuring packages
-;; - `after!' for running code after a package has loaded
-;; - `add-load-path!' for adding directories to the `load-path', where Emacs
-;;   looks when you load packages with `require' or `use-package'.
-;; - `map!' for binding new keys
-;;
-;; To get information about any of these functions/macros, move the cursor over
-;; the highlighted symbol at press 'K' (non-evil users must press 'C-c g k').
-;; This will open documentation for it, including demos of how they are used.
-;;
-;; You can also try 'gd' (or 'C-c g d') to jump to their definition and see how
-;; they are implemented.
-
-;; Set emacs logo as the default image
-(setq
- +doom-dashboard-banner-file (expand-file-name "logo.png" doom-private-dir))
+                  ;; Doom exposes five (optional) variables for controlling fonts in Doom. Here
+                  ;; are the three important ones:
+                  ;;
+                  ;; + `doom-font'
+                  ;; + `doom-variable-pitch-font'
+                  ;; + `doom-big-font' -- used for `doom-big-font-mode'
+                  ;;
+                  ;; They all accept either a font-spec, font string ("Input Mono-12"), or xlfd
+                  ;; font string. You generally only need these two:
+                  ;; test
+                  (setq doom-font (font-spec :family "monospace" :size 28)
+                        doom-variable-pitch-font (font-spec :family "sans"))
+
+                  ;; 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. These are the defaults.
+                  (setq doom-theme 'doom-one)
+
+                  ;; If you intend to use org, it is recommended you change this!
+                  (setq org-directory "~/org")
+
+                  ;; If you want to change the style of line numbers, change this to `relative' or
+                  ;; `nil' to disable it:
+                  (setq display-line-numbers-type t)
+
+
+                  ;; Here are some additional functions/macros that could help you configure Doom:
+                  ;;
+                  ;; - `load!' for loading external *.el files relative to this one
+                  ;; - `use-package' for configuring packages
+                  ;; - `after!' for running code after a package has loaded
+                  ;; - `add-load-path!' for adding directories to the `load-path', where Emacs
+                  ;;   looks when you load packages with `require' or `use-package'.
+                  ;; - `map!' for binding new keys
+                  ;;
+                  ;; To get information about any of these functions/macros, move the cursor over
+                  ;; the highlighted symbol at press 'K' (non-evil users must press 'C-c g k').
+                  ;; This will open documentation for it, including demos of how they are used.
+                  ;;
+                  ;; You can also try 'gd' (or 'C-c g d') to jump to their definition and see how
+                  ;; they are implemented.
+
+                  ;; Set emacs logo as the default image
+                  (setq
+                   +doom-dashboard-banner-file (expand-file-name "logo.png" doom-private-dir))
 
 ;; Saves emacs backups in other folder
 (setq
diff --git a/.doom.d/init.el b/.doom.d/init.el
index e194d0c7..a5636ff9 100644
--- a/.doom.d/init.el
+++ b/.doom.d/init.el
@@ -1,3 +1,10 @@
+;;
+;;  | '__/ _ \ / _` / __|    Roger González
+;;  | | | (_) | (_| \__ \    https://rogs.me
+;;  |_|  \___/ \__, |___/    https://git.rogs.me
+;;             |___/
+;;
+;;; $DOOMDIR/config.el -*- lexical-binding: t; -*-
 ;;; init.el -*- lexical-binding: t; -*-
 
 ;; Copy this file to ~/.doom.d/init.el or ~/.config/doom/init.el ('doom install'
diff --git a/.doom.d/packages.el b/.doom.d/packages.el
index 15663a04..88818708 100644
--- a/.doom.d/packages.el
+++ b/.doom.d/packages.el
@@ -1,3 +1,10 @@
+;;
+;;  | '__/ _ \ / _` / __|    Roger González
+;;  | | | (_) | (_| \__ \    https://rogs.me
+;;  |_|  \___/ \__, |___/    https://git.rogs.me
+;;             |___/
+;;
+;;; $DOOMDIR/config.el -*- lexical-binding: t; -*-
 ;; -*- no-byte-compile: t; -*-
 ;;; $DOOMDIR/packages.el
 
@@ -12,35 +19,35 @@
 ;; Here are a couple examples:
 
 ;; To install SOME-PACKAGE from MELPA, ELPA or emacsmirror:
-;(package! some-package)
+                                        ;(package! some-package)
 
 ;; To install a package directly from a particular repo, you'll need to specify
 ;; a `:recipe'. You'll find documentation on what `:recipe' accepts here:
 ;; https://github.com/raxod502/straight.el#the-recipe-format
-;(package! another-package
-;  :recipe (:host github :repo "username/repo"))
+                                        ;(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")))
+                                        ;(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, for whatever reason,
 ;; you can do so here with the `:disable' property:
-;(package! builtin-package :disable t)
+                                        ;(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"))
+                                        ;(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 raxod502/straight.el#279)
-;(package! builtin-package :recipe (:branch "develop"))
+                                        ;(package! builtin-package :recipe (:branch "develop"))
 
 
 (package! whitespace-cleanup-mode)