larrasket

It's a feature that I miss from Clion, my current workflow is by using a 3rd party linter after my coding session outside of Emacs. I know that I can use the linter with an after-save-hook, but is there any other solutions with flycheck or lsp integrations? (I tried flycheck-clang-tidy but I didn't get any warrings or indicators, not sure if clang-tidy can detect them though)

I've been looking for methods to improve Emacs performance especially with my configuration being over >3k. I'm not particularly interested in startup-time since I never close Emacs. Here's what I found so far

(setq package-native-compile                            t
      gcmh-high-cons-threshold                          100000000
      gc-cons-threshold                                 100000000
      scroll-conservatively                             101
      jit-lock-defer-time                               0
      large-file-warning-threshold                      nil)



(add-hook 'after-init-hook #'(lambda () (setq gc-cons-threshold (* 100 1000 1000))))
(defvar gc-timer nil)
(defun salih/maybe-gc ()
  (let ((original gc-cons-threshold))
    (setq gc-cons-threshold 800000)
    (setq gc-cons-threshold original
          gc-timer (run-with-timer 2 nil #'salih/schedule-maybe-gc))))

(defun salih/schedule-maybe-gc ()
  (setq gc-timer (run-with-idle-timer 2 nil #'salih/maybe-gc)))

(salih/schedule-maybe-gc)

I can tell that I've noticed some improvements.

Some four years past, my life was simple. I used of vim .. occasionally found refuge with jackbrains IDEs, used a splendid open-source calendar application and notion for note taking. That was life.

But, lo and behold, there arrived a fateful day, when I, in my quest for a PDF viewer capable of illuminating the sacred texts with vibrant cute yellow highlights, did consult the Arch Wiki. And thus, the sacred scripture of the wiki proclaimed it: "GNU Emacs, sire!" From that moment forth, my existence was irrevocably altered, and my life took on new meaning.

Forsooth, as I contemplated, there existed nary a tool that could attain the heights of my own prowess, as witnessed within the hallowed confines of elisp.

Yet, as the days and years flowed onward, a vexing truth did unfurl its troubling wings within the chambers of my soul. A discontent gnawed at the edges of my being, for the enchantment of Emacs held me captive, leaving me bereft of escape. All else that I encountered in the vast expanse of digital tools and systems seemed archaic and disordered when placed in the shadow of Emacs' grandeur.

For while I marveled at its limitless capabilities and intricate wisdom, I remained forever unsatisfied. Each quest for efficiency led me deeper into its labyrinthine depths, where an insatiable hunger for perfection persisted, much like the boundless sea whose depths are never truly plumbed.

A ceaseless longing for a more refined configuration, a more potent package, or a more elegant elisp blocks danced within my thoughts. The very thing that had once set me free, had now become the golden cage in which I resided, unable to break its enchantment and return to a world of simplicity and contentment.

Let it be known, O ye novices who venture into the alluring embrace of Emacs, heed the tale of my journey as a cautionary fable. For, as you traverse the path of this venerable text editor, be mindful of the siren song that sings of boundless power and unparalleled control. The allure of Emacs, with its arcane keybindings and vast sea of extensions, may cast a potent spell upon thy heart.

be wary, for it can ensnare thee in a web of complexity and unending quests for perfection. The very attributes that grant thee mastery may, in turn, become the chains that bind thee in an eternal quest for more. As you delve deeper, the simplicity you once knew may fade into obscurity, and other tools may appear dull and obsolete in comparison.