Quoting Ben Kavanagh <[email protected]>: > Yes, any package providing tag-keyword indexing would have to address > this. There are ways to handle this, using caching of index and index > reconstruction on save. Per mentions this in a later message. >
Right, I should have thought about this a little longer. etags provides this kind of indexing for function and variable names in source code. > I had looked at this briefly. I just took a second look because of your > message. This seems a good solution but it is missing connectivity to > muse. For me the reference entry is a place to do the following > > 1. Discuss main ideas of paper. > 2. Link to wiki (muse) pages on these main ideas > 3. Link to related papers. In particular > * most important papers that led to this development > * most important papers that came from it. > 4. Link from wiki pages to reference > > Based on my brief look so far refdb provides (1) by allowing to enter > extended notes. It does not appear to provide the others. > It does (4) too, whereas (2) and (3) are doable but in a less-than-desirable fashion currently (i.e. you wouldn't want to do it). My planner-mode protocols and method sheets all contain links to references, usually as a citation key. This is a string like "MILLER1999". You can mark this citation key with your mouse and call a RefDB command to display this reference. > > I will take a look at the current emacs mode for refdb and try to > determine how much work this would be. > I haven't fiddled with refdb-mode for a while, but if this is a useful path to follow for your needs, I'll see if I can help. regards, Markus -- Markus Hoenicka [email protected] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de _______________________________________________ Muse-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/muse-el-discuss
