It is definitely a pit! However, the info table of contents is very well laid out. What I usually do when I don't want to go too deep into the pit and am curious if what I want is in there is to go to the main directory using C-h i d, and then press m, type org, and press return. That gets me to the top org page, and then I just press m, and browse the options with the arrow keys. Usually, just looking at the main level menu gives me ideas oh which path to choose, then I press return on that, press m again, etc. Hope this helps you chart a path through the pit! Sent from my iPhone > On Feb 12, 2024, at 18:45, Robert Melton <lists@xxxxxxxxxxxxxxxx> wrote: > > Whelp, I completely didn't know about this feature, and it is a hugely helpful. > > I deeply worry I will fall into a org-mode pit and not come out for a few days. > > I have barely scratched the surface or org. > > > >> On Feb 12, 2024, at 10:45, Parham Doustdar <parham90@xxxxxxxxx> wrote: >> >> Hey Robert, >> Not sure if you know this, so putting it here in case you don't, but the things you list under your "can get clever" are actually very easy to do with no coding. Just bind org-capture to a global hotkey, then press it when you want to make a note about the line you are just reading. Then you can insert the link in an org buffer using C-c C-l I think, and the line you had captured would be in the history, which you can go through using the arrow keys. >> Also, what I often do is keep my notes open in a separate window (or tab in MacOS terms) by pressing C-x 4 b. Then I can use C-x o to jump between the code (open in one window) and my notes (open in another window). >> I'll leave the rest to others to answer, as I often struggle with spaghetti code myself.' >> Sent from my iPhone >> >>>> On Feb 12, 2024, at 16:34, Robert Melton <emacspeak@xxxxxxxxxxxxx> wrote: >>> >>> Curious if there are any recommendations for learning new codebases. >>> >>> I am currently fighting a rather complex codebase for a web app and wondering >>> if the community has any tricks for staying sane when trying to spin up on new >>> projects. >>> >>> Thus far I have played a good bit with folding, which I like the idea of because >>> it makes it easy to skip over or dig in on a block, and while I like the notion of >>> it, I hate the actual experience. >>> >>> Right now, I am mostly maintaining a notes file on the project as I go and >>> learn each piece, can get clever I think and drop links into the files, or >>> even sort of build my own annotate by binding a keypress to jump to my >>> org file and come back. >>> >>> Any tools or techniques I should add to my bag of tricks? >>> >>> -- >>> Robert "robertmeta" Melton >>> lists@xxxxxxxxxxxxxxxx <mailto:lists@xxxxxxxxxxxxxxxx> >>> Emacspeak discussion list -- emacspeak@xxxxxxxxxxxxx >>> To unsubscribe send email to: >>> emacspeak-request@xxxxxxxxxxxxx with a subject of: unsubscribe > > -- > Robert "robertmeta" Melton > lists@xxxxxxxxxxxxxxxx >
|Full archive May 1995 - present by Year|Search the archive|
If you have questions about this archive or had problems using it, please contact us.