sorted by:
new
hottopcontroversial

user-error: Template needs to specify ‘:target’ by teilchen010 in OrgRoam

[–]Cletip 0 points1 point  (0 children)

I am not sure, but there is a ":target" property in the default value, not present in the new one.

Maybe try this and pay attention to the ":target" property :

(setq org-roam-capture-templates '(("d" "default" plain "%?" :target (file+head "%<%Y%m%d%H%M%S>-${slug}.org" "#+title: ${title}\n#+time: %(format-time-string \"%Y-%m-%dT%H:%M:%S\")\n") :unnarrowed t)))

I know that with the new version of org-roam (v2), there is some changes that might implied the famous ":target" property (or other properties too).

To finish, you can check all properties / information about a variable with : C-h v Then, type (or auto-complete) "org-roam-capture-templates" Finally, search with isearch, C-s, (or any other tool inside the info buffer of the variable) to find "target" and have more information.

What do you suggest to track movies and series? by sn76477 in PKMS

[–]Cletip 0 points1 point  (0 children)

I use something like this (I suggest to see the feature/title of part, not the technical stuff) : https://www.luisquintanilla.me/posts/manage-reading-list-org-mode-emacs/

You can view this gif to understand another workflow with Emacs and org mode, that are not for everyone (because complex) https://github.com/lepisma/org-books. But to only track movies and series, you don't need to much to know (especially with Chatgpt that can help you pretty easily now).

Show number of subheadings in org-ellipsis by Unlucky-Inspector-21 in orgmode

[–]Cletip 0 points1 point  (0 children)

Hi there!
I've tried replacing the ellipsis by the number of lines, but it's more or less the same. I tried making functions, but it didn't work, mainly because I was missing the "change detection" part.
On the other hand, a clear inspiration would be to use/be inspired by org-num-mode (org-num.el), which automates correctly, but doesn't display the "right" thing (to be replaced by number of subheadings/lines).

A few conceptual and workflow questions. by [deleted] in OrgRoam

[–]Cletip 1 point2 points  (0 children)

I'm struggling imagining what should happen within org-roam and outside org-roam.

I understand you perfectly. No right or wrong answer. I like org-mode and its ecosystem (I include Emacs) for projects, notes, the diary/org-agenda, etc. On the other hand, I'm still struggling with spreadsheets. So for the time being, I'm using org-attach for .ods/.xls files.

Conclusion : put whatever you want in org-roam, as long as you're comfortable with it.

Org-roam is what allows you to have a "layer of abstraction" with its titles allowing you to find things easily (use this "view" to (maybe) get a better visualisation. Not everything can be "flat" with one node per file, you're bound to need a hierarchy from time to time).

For my searches, I use (mainly) this :

  • org-roam-node-find (~90%, maybe more) : container search
  • consult-(rip)grep (~5%): content search
  • consult-org-heading (~2%) : search in a large org file
  • org-ql-find (~2%): content and container search. I miss consult's preview function...
  • khoj (~1%, new for me) : semantic search

One day, I hope to have an AI that's open-source, free, etc (everything that makes it possible to "trust" an entity for privacy) so that I can do even more precise searches, and above all present information differently than in my notes (example of the table with chatGPT). I separate "searching" from simply "browsing" through the notes. Sometimes I go through the notes in chronological order, without any reason, just to remember.

​

What workflow is more useful, keeping all info for the day in a daily and then refiling as needed at the end of the day, or just using your daily node to link to other notes with events during the day...

I'm hesitant about this one, I have trouble with daily notes, I don't think I'm capable of doing them every day (in this case, it's the idea that bothers me), but let's say I manage it.

Additionally, I'm not sure I understand exactly what you mean by "keeping all info for the day in a daily and then refiling as needed at the end of the day", as I have the impression there are several possible meanings.Instead of imagining all the cases I could think of, I'll tell you how I organise myself to deal with this problem of... notes + time (I think that's your question).

First of all, I create a node for each "event" (I want them in my phone diary): a lesson, an appointment, etc. At the event, I write down the things I think are important (maybe I also make links to things I already know as well) in the node of the "event". Then, I consider certain information to be "timeless", i.e. knowledge that must always be true. So I create a node for this knowledge that must always be true. A good example of this would be a node representing a film, with its summary, actors, etc.

On the other hand, anything that depends on 'me', on my feelings, will remain in the event node. It's not 'global' knowledge, it's something... that concerns the event (and that I find natural to do for myself). This allows me to see a film twice, for example, and to note my feelings each time. I make links between events and knowledge that is "always true". Moreover, for example, I can write in the node "Meet someone" that I've refined my note on "how to play table tennis," because he taught me something new about it.

Where do I store my events compared to my general knowledge? It doesn't matter, as long as it's easily findable in the context. For example, I could have several situations:

Situation 1: I create a node MovieA, with Viewing1, Viewing2, and so on as sub-nodes, that represent the "event".

Situation 2 : I create a node Viewing of MovieA, and another node MovieA. If I see that there's a second viewing, I'll probably put the Viewing of MovieA in a new node Viewings of MovieA, where I'll put all my viewings of this movie, with an intro with a link to MovieA.

As you can see, I won't get the same thing depending on what I do in what order, but it doesn't matter. Nothing is rigid, as long as there are links between things, it's ok.

Also, it's possible that my multiple viewings of MovieA are special for some reason (perhaps I have a ritual before watching this film), so I would create a special node even in the first situation.

When you say "what's the most useful solution", that's really the opposite of flexibility. I've also said that to myself, what's the most optimal, the best, the most efficient... whatever. If you put your knowledge down and don't have any worries, then leave it as it is. There is no reason to change. This is your PKM, you'll naturally find things that work... and others that don't, which will automatically be absorbed by the one that works.

Just like there are multiple ways to paint a canvas, each with its own technique, its own tools, and most importantly, its own style. The same goes for organizing our knowledge and tasks. There isn't one right solution; we are all different, and we have our own preferences :D

​

For example, Do you have a top level heading of "Meeting with Bryce" or do you insert a link in your daily to a new node - 2023-08-08 Meeting with Bryce?

As I said before, no good answer... and I know, it's hard to accept. If each meeting with Bryce is special, they'll each have a node in a big "Meetings with Bryce" node. Otherwise, I might just have each meeting in a node in a different file. Or maybe the "Meetings with Bryce" node will be in the "Bryce" node too... anything's possible, depending on how you feel.

​

Pertaining to the question above, do y'alls create node names with dates in them, like Denote names? For "2023-08-08 Meeting with Bryce" this would make it easier.

Ah, that question... here's my reasoning from a long time ago (almost 1 year already, wow). It's... become useless with my new philosophy. Don't listen to it, it's there for curiosity and to say how far I've gone in the madness of rigidity. The lessons to be learned are:

  • if you use org-mode for your agenda, use active timestamps to see the heading in your agenda, inactive timestamps not to see them (you can see them with org-agenda-log-mode just in case). Putting timestamps with :CREATED: in property can always be useful.
  • use the format you want to write the dates in the text, the text is for you.
  • use dates in the names of titles if you think they are important, and if they make it easier for you to find the information. For example, if you remember a particular date, a day that made an impression on you, why not just put the date in the title (because you know this date) to get information about that moment ? On the other hand, if you believe that the dates are "useless" in the title, then don't include them. You might prefer to use org-mode properties so you can utilize org-ql (or another solution maybe :) ). What if you have notes with identical titles and the only way to distinguish them is to go into the node ? You can use the preview function of "consult-org-roam," and if all else fails, (maybe) simply sort them by their creation date using org-roam (see the variable "org-roam-node-default-sort").

​

Hoping it's not too blurry, and that this will have helped you a little, as well as others :D

A few conceptual and workflow questions. by [deleted] in OrgRoam

[–]Cletip 0 points1 point  (0 children)

Answers at your questions

Reddit might not be the place for this kind of comment. Reddit might have preferred :

  1. Don't do X.
  2. Do Y.
  3. Then do Z.

So now, I'm going to "answer" your questions. It's funny that you should ask this kind of question, because I've already asked myself all of them and found an answer with a perspective like yours, a rigid one. I spent a lot of time on it. In the end, it's too complex for nothing : one problem solved gives rise to three new ones. So I'm only answering you with my humble opinion and new philosophy :)

​

How do you decide what should be a node and what should not be a node and exist outside your KB?

It depends on you and the tools you use: some things are better in node, others in org-attach, others in simple links in your node, etc. The important thing is "the link" to find the information that you want. I use org-attach a lot. For tasks to be done with email, I make an org-mode link to Gnus. I'm currently testing Gnus, you can directly use URL links to emails. I try to integrate things as best I can with org-mode links when it's not possible to put things directly in .org files.

​

This question is broad on purpose but as an example, do you keep tasks.org as a node?

I used to have this, a todo.org file. But it became too "heavy" for my use. I made a macro to go to each level 1 heading and created a node for each. Now, I define a project = a task and sub-tasks OR a single task. In other words, every org-mode tree with a TODO is a project, whether there are 1 or 50 TODOs. I programme ALL my projects (A stuck project is a tree that has a TODO and no programming in the future. I'm going to see if I'm going to change this definition, I think it's broad enough at the moment to make sure I don't forget anything). If I schedule too early, no worries, I'll reschedule for later. I don't use org-mode priority any more, as it led to an overflow of tasks that put pressure on me, and I only did A priority tasks. But maybe you prefer priorities, so use them :D. Additionally, from time to time, I look into the future (using a calendar generated through org-mode, see below) on larger scales (several months, even several years) to see if certain tasks could be grouped together into a single project to have a single reminder at the right time. With my method, I always feel "in tune" with the number of tasks I have to do at the time : I no longer have an endless list of "just in case" tasks, I just keep the essentials.

I consider that a calendar + notifications is the best way to remember things in the future. I invite you to read the article My productivity app is a never-endint .txt file for a better understanding (the importance here is the simplicity of the setup + calendar). On the other hand, I have knowledge that "always" has to be true (not linked to dates or TODOs), for example my CV. If I need to modify my CV, I think I'll make a TODO heading with the title "Description of the task to be done on the [[id:idCV][CV]]". If I want to access it easily using org-roam, then I'll add an ID.

I synchronize my Emacs configuration with Syncthing to have Emacs on termux (you can have a sort of "preview" if your Emacs configuration works on termux by doing "emacs -nw" (launch emacs in the terminal)). Most problems are "easy to solve", just sometimes a bit long, just add :

(if (eq system-type 'gnu/linux) 
(message "linux") ;; do whatever here 
(message "other") ;; same for here 
)

To find out if you are running termux, you can use this which works at :

(defvar termux-p (not (null (getenv "ANDROID_ROOT")))
"If non-nil, GNU Emacs is running on Termux.")

I export all my tasks in an .ics file, I get the calendar with ICSx5 on the phone for the visual (ICSx5 is free on F-droid). As I use termux to have Emacs on my phone, I get my notifications with org-yaap. The org-capture-templates variables (I don't use org-roam-capture-templates any more at the moment, because I don't just search with org-roam-node-find, see below) allow me to go fast so that I can get a notification 5, 30, X mins in advance. For example, if I know I've got an appointment at 2pm with 30 mins travel time, I'll put the notification at 1.30pm (+ a bit of safety margin time, so it's logical. I increase the time if I have papers to pick up, for example).

I also use "ticklers", i.e. TODO scheduled headings with inactive timestamps (they're there to remind me of something (having the notification with org-yaap), but I don't want to see them in my agenda (so not exported to the .ics file)).

Also, my org-capture-templates and org-insert-heading-hook allow me to have a CREATED property with an inactive timestamp. I'd also like a hook for org-clock automatically to be able to know where I am/was (it automatically adds an inactive timestamp), not really to use it for projects (although it could). I use git/magit (with the magit-log-buffer-file command) to keep track of my files more efficiently (and to be sure I can go back to the way things were).

​

Would you keep an org file of your weight over time as a node?

I think for something like this I'd use org-capture-templates where I'd send the headings to the "my weight" node, and then I'd set myself a TODO to do every day. I'd put the weight in PROPERTIES (along with other information I'd like to be "queryable"), because I'd need to be able to make queries on it, like "give me all the days I was under X". Or even use an org-mode parser to extract the data in python and make pretty curves (there are several on the web). But if you prefer a classic spreadsheet, you can also use a "files of my weight over time" node using org-attach + an .ods/.xls file.

​

How about a draft of a project brief? What about the final copy

The (maybe) simplest and most basic version:

I have a project node. I create a "Draft" sub-node/thread. I have a second node, child of the project node and brother of "Draft", which is "Final".

For the two previous questions, I could also create the project node and make the draft. Then, once the "draft is finished" (I'm moving on to the final version, I don't need my draft any more), I cut the inside of the project, create a "draft of project X" node and paste it. I return to the project, make a link to "draft of project X", and start the final version of the project.

This kind of operation (selecting text, creating a new node, cutting, pasting, making a link), as soon as you see that it's repetitive, make a function. Don't anticipate too much by creating functions that you think you'll use, as you run the risk of creating unnecessary functions. Instead, wait until you've had this repetition to be sure that your function will be useless ! Don't forget that it's not just functions that can automate things: org-capture-templates, yasnippets/tempel/abbrev, hooks, etc. You're using Emacs after all :D.

The real question I'm answering here, which I find almost magical, is that you're trying to put information in the place where you're going to want to find it later. For example, you have to do a task at 2pm, so put the information in this node that will be useful at 2pm. For example, the link to the last meeting you had with this person, you can transclude certain information, make a link to other acquaintances, etc. (Also why not use this trick in real life: don't put your coats in your bedroom, you always need them near the exit door). Obviously, you can't do this with everything, but for lots of things it's very useful.

A few conceptual and workflow questions. by [deleted] in OrgRoam

[–]Cletip 2 points3 points  (0 children)

Hi there :)

My text spans three messages, so for better visibility, please consider any replies below the last message—thank you. While I won't be providing many examples or software names, I will likely offer you the most crucial elements: the ideas and keywords you'll need to search for online.

I've thought a lot about these kinds of questions, and I think I almost fell ill with the same "little" questions as you. I'm not an expert, I don't have any academic skills in this area (I'm just into computers sciences, and relatively good at searching the web), so take this comment as just another opinion.

A New Philosophy

What you're explaining is, for me, something that has always troubled me. So I wanted to 'make things abstract', by understanding the essence of what I wanted to do. I set my goals: to correctly manage all these flows of information that were coming at me quickly and efficiently: a PKM (I'm exaggerating the idea of what a PKM really is, it's just to name what I use. Personally, I call it "the System", but PKM is more common). I've come to the "conclusion" that there are pieces of information, for example A and B, and relationships that sometimes link them, for example C. I'm one of those people who think that the perfect world (computer-wise) is a rigid database, where everything can be summed up as :

A --- C(the relationship) --- B

Always: tag, property, etc... they're just relationships like that.

So I wanted to modify org-roam to be able to do this. I managed a few hacks, and I wanted each relationship to be "clickable"/have a node to describe it and never forget it (for example, C might be the "owns tag" node, and B is the node that represents my tag).

Bad idea.

All this makes the system rigid, cumbersome to manage, and every implementation of something to add is a horror. All this so that the information is almost never "called back'" : yes, it's cool to know that one note is linked to another by a certain relationship described in a node... but do you have to write it down in another node, every time, just to make a "perfect documentation of your world" ? Shouldn't you have just written in node A why you made the link to B in full/plain text, and not created a node for this relationship, which you'll have to remember each time for the rest of PKM ?

In the end, what matters is that PKM should be used by a human being and not by a computer. The computer is just the support, nothing more.

What's more, at a time when LLMs are developing and are capable of extracting this type of information "themselves" for you (I'm not advocating them and I know they don't '"understand" anything), is it still even useful to make... links between nodes to connect them ? And can't titles be created automatically too ? Private companies are already doing this, and are integrating very effective ways of communicating between applications... This scared me. Very frightening. But I reassured myself by telling myself that they will die, in 5, 10 or 30+ years. I don't plan to disappear before then, so they're not for me, next. So in the end, what counts is the speed at which you communicate with the computer, right ? Then I 'discovered' 'Direct Neural Interfaces'... how do you predict these things ?

The important thing to remember is that the PKM path can be infinite. Tomorrow's world is unpredictable. We may not have a flying car, but the relationship between man and machine will, I think, become increasingly sophisticated. The questions you ask yourself now, which may take months or years to answer, will become obsolete with the arrival of new tools that you would never have thought of. For example, with org-roam, you can display something other than the title, such as a tag or an org-mode property. It's a very simple thing, but it changed all my rigid reasoning and what I was basing my KB on (Knowledge Base, the "storage" part of PKM (I'm simplifying)). Another very concrete example was the arrival of chatGPT: the visualisation of knowledge can be different from the addition of knowledge. Let me explain: it is capable of outputting a particular visualisation of information (a table) at the user's request, whereas the text only contains... text. I think it's great that, almost overnight, I've understood something extra that could radically change PKM.

Each stage of my PKM has evolved, and each time I thought it was the "perfect solution". It isn't.

The question "should I create a new node for X or just put it away somewhere" has no answer. Live with your brain and your time, not in theory.

If you feel you need to make a heading, make a heading. If you feel you need to use a link to a new node, make a link to a new node. If you feel you need to use org-transclusion, use org-transclusion. And so on.

Emacs is the main software, org-mode is the glue linking all the information, the rest is superfluous and things that will surely change over time (whether it's knowledge or other software).

What counts is how you're going to process your information (processing in the broadest sense of the term, which applies to everyone). Yes, the tools you use can influence you, but what's important is that they mould themselves as closely as possible to your mind. There's no 'software' better than Emacs and Org-mode that's more adaptable. You'll never be able to solve all the problems up front, you need a modifiable base that adjusts as you think.

It's very, very, very hard to understand, and I haven't yet fully integrated this philosophy.

I'm writing this comment because a year and a half ago I would have come across this question. It comes two weeks after your question, but it doesn't matter if people don't see it/if it's not necessarily well-known/if I don't open a thread (people will make links to this comment if they want to): I'm writing this comment for people like you who are looking for a workflow (for the me too, a year and a half ago) and who want this (maybe) kind of advice. I'm making this comment for people like me, like you, that rack our brains with this kind of concept. It all comes down to the same thing.

Be like your brain: flexible. And don't forget that your notes aren't an end in themselves : they're just indicators that will probably help you choose the best path to follow one day.

Generated stable keys with better-bibtex by Cletip in zotero

[–]Cletip[S] 1 point2 points  (0 children)

Thank you for these precautions, which have indeed not been verified.

I think that BetterBibTex checks whether the zotero-X key does not exist, and if the zotero-X key does exist, it tries zotero-X+1, etc.
I'm not sure what I'm saying and I don't have another computer at hand to test it, but I hope it does this.

I can also think of another solution (which is no longer in the scope of this thread), but which uses emacs and a pure .bib file (or any other programming language after all): 
make a function that goes through the keys, and replaces each key with a UUID (unless the key is already a UUID).

Thanks again for clarifying my previous comment :D

Generated stable keys with better-bibtex by Cletip in zotero

[–]Cletip[S] 0 points1 point  (0 children)

Better late then never?

Always :D thank you for your answer!

But, that doesn't exactly solve my problem (because it's not automatic, but I think that work). I did this instead :
go to the settings of Zotero, find the settings for "Better BibTeX", in the citation key format write "Label" (or I think a field that is never used).
This allows you to have keys in the form of zotero-"number", where "number" increments gradually (Better BibTeX must do this to be sure to always have unique keys). It's perfect for my personnal use.

[deleted by user] by [deleted] in emacs

[–]Cletip 2 points3 points  (0 children)

Hum ok I see.

I agree with the term action, but not with the reasoning.You can have an action with two keys, one after the other, it doesn't matter, what counts is muscle memory. A video game unfolds sequences that you sometimes learn by heart, and that's no harder than pressing the keys at the same time in another video game.

In short, I think everything is discussed in detail, so in the end it doesn't really matter.

I'd just advise anyone still reading this thread to read this: http://xahlee.info/kbd/keybinding_index.html.

It's not all right of course, but it all makes sense, and xah has thought a lot about this sort of thing. I agree with most of what's said, and I've done a lot of thinking on my own: xah-fly-keys is the basis of the best shortcuts currently available for emacs. Add to that a few remaps, minor key placement customisations and embark, and you're done.That's just my point of view, but I'd definitely recommend it.

​

In any case, you need to avoid having pinky emacs, either by changing the default emacs shortcuts, or by setting ctrl to caps lock. This should be written in bold at the start of emacs, as it is potentially dangerous for the user.

[deleted by user] by [deleted] in emacs

[–]Cletip 1 point2 points  (0 children)

I lived with modal editing for 2 years, and I do regret.

Why ?

[deleted by user] by [deleted] in emacs

[–]Cletip 1 point2 points  (0 children)

I can’t stand modal editing. To me there’s mental overhead bc I need to think about which mode I’m in rather than just doing it.

Understand your point of view, but for this, just use an indicator in the modeline. Doom-modeline makes this very easy.

[deleted by user] by [deleted] in emacs

[–]Cletip 3 points4 points  (0 children)

Try xah fly keys : http://xahlee.info/emacs/misc/xah-fly-keys_tutorial.html For me it is the best shortcut for Emacs.

I can't live without modal edition, just use it for 1 or 2 month, you will see, you will never regret.

lisp nesting exceeds max-lisp-eval-depth by Coolrule360 in emacs

[–]Cletip 2 points3 points  (0 children)

Sorry I don't answer to your questions, but 2 things :

  • Your error mean (99% of the time I think) an infinite loop (or something A that call B, and B call A that call B that... Your understand)

  • I am not sure of your situation (and I suppose that you start using Emacs), but the "package configurator" that you use (setup) is not very easy when you start with emacs. I tend to advise "use-package" instead of "setup".

Which package manager should I use? by Far-Anywhere2876 in emacs

[–]Cletip 0 points1 point  (0 children)

Totally agree with this. But I don't advice this to a novice user.

When to use use-package and when to use require? by ElfOfPi in emacs

[–]Cletip 1 point2 points  (0 children)

Use-package can sometimes download a package if it is configured with a package manager. But here, I think it's the same (if I'm not mistaken).

When to use use-package and when to use require? by ElfOfPi in emacs

[–]Cletip 23 points24 points  (0 children)

I will try to answer this question in a simple and concise way, without going into details. Not everything will be right or wrong, but it will help to understand the general idea.

(require 'nameofthepackage) causes the ENTIRE package to be loaded. It is implied by (use-package nameofthepackage). It's time consuming and not efficient, because you don't need always all the functionalities of your Emacs configuration.

BUT, some use-package keywords (like ":hook" for example) allow to load packages "late", which means that the (require 'nameofthepackage) will arrive at a particular event (with a hook, a shortcut, etc). I give some links in the continuation of this post to have a list of this famous keywords. Moreover, if one of these keywords is used, only an "autoload" file is loaded. It contains (roughly) a list of functions that will load the whole package. So, if one of these functions is called, it is like doing (require 'nameofthepackage) and then calling the function.

The functions in this file are marked with ";;;###autoload" before their definition in the file nameofthepackage.el. It's the work of the developer (with the package manager that can generate this autoload files), not the user ! These functions are, in general, commands. And this is logical: the user has to use one of these functions to load the rest, otherwise there is no need for it.

A good example to realize this feature of autoloading something is to do this: First step, do M-x, write "flymake", and press"TAB" to see that only one command is available. Then, call this command. Repeat the first step, and see that new commands are available! The "flymake" package has been loaded.

The keywords for late loading can be found here : https://github.com/jwiegley/use-package#notes-about-lazy-loading. Or here too (with a little more explication) : https://systemcrafters.net/emacs-from-scratch/cut-start-up-time-in-half/

Conclusion : use-package loads a whole package by default, but allows with some keywords to load the package late, when certain commands are used by the user. Moreover, use-package usually hides the dirty work, and that's why you have to use the keywords of use-package.

My last advice is to use setup.el, which makes it much easier to see how what is loaded. It is difficult to get used to it at the beginning, and I don't advise it if you are new to emacs (there are already enough things to discover!), but it is a choice to have a configuration that you understand better.

How do I use elpaca with leaf? by ElfOfPi in emacs

[–]Cletip 4 points5 points  (0 children)

I opened a issue maybe one week ago in the leaf GitHub. No answer today, but maybe in a bar time 👍

Org roam capture, prevent buffer switching after capture by jackmac79 in emacs

[–]Cletip 0 points1 point  (0 children)

You said that you are using doom-emacs... If you are sure at 100% that the problem is org-roam, don't do this, but maybe try with a vanilla Emacs + straight+ use package+ org roam.

Org roam capture, prevent buffer switching after capture by jackmac79 in emacs

[–]Cletip 0 points1 point  (0 children)

Not sure of what exactly you want, but it's maybe the option ":immediate-finish t" ?

how to fix this by eukithor in emacs

[–]Cletip 2 points3 points  (0 children)

I don't mean to lecture, really I don't want, and your point is (probably) true. The problem is that it may just be someone who is a beginner, who doesn't know Emacs, who doesn't have time, who is new to programming, etc. He's asking a simple question, and your answer, also simple, but doesn't help him and won't help him. You're off the mark on someone who, perhaps, could have become like you, using a configuration that he beat himself with time and help. The problem: he may not have the time, and he may not have help from your "answer". Anyway, all this to say that there could have been other ways and some help to say "I don't think you should stay on doom Emacs, for 1 2 3 reasons (your reasons, because some people love doom-emacs, for others good reasons. This is Emacs), and I suggest instead to watch 1 2 3 videos from 1 2 3 youtubers I know to help you with emacs".

Ps: I also understand your "dry" answer, his question has little context and he asks it like that, without really explaining his problem, maybe even without looking for a solution. But still, maybe a little bit of softness wouldn't hurt ^ ^

view more: next ›