Re: Org mode for meeting minutes
Hi Timm Timm Lichte writes: > Just for your amusement: I've developed a very different but effective > way of taking minutes with org-mode that uses just lists and > enumerations. I have been using this solution for more than a year on > a daily basis and I'm really happy with it (and colleagues don't > complain). Speed, simplicity and readability for non-emacsers is > critical in my job, so the solutions you are proposing would be > overkill. This is really interesting! I can see that you are very efficient with this. I think my solution is more using the standard org-mode infrastructure, I don't define any export for example. > You can have a look at the style and code here: > > https://github.com/timmli/org-minutes-dev If I understand correctly you are defining some kind of extra list markup (is something a task or a decision, etc) and the you wrote a custom exporter that produces fancy LaTeX for the minutes (well, if I understand correctly it really is a custom exporter that generates org-mode and then LaTeX from there). I don't quite understand how the LaTeX works. Is this some kind of two column layout or do you keep the action item markers and the assignees in the margin? Can you post the produced LaTeX? > Any feedback is greatly appreciated. But keep in mind that the code is > not polished at all -- this is a hobby project of an elisp dilettante. It would be good to package this. The code would get more usage and you'd get more feedback. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: Org mode for meeting minutes
On Monday, 23 Mar 2020 at 21:03, Timm Lichte wrote: > You can have a look at the style and code here: > > https://github.com/timmli/org-minutes-dev This is also very nice! I wish I'd had either of these solutions when I used to take minutes... I know have somebody take minutes for me when I chair meetings. ;-) -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.6-433-g4b2628
Re: Org mode for meeting minutes
Nick Dokos writes: >> I have an off-topic query though: How do you right align tags? > , > | org-tags-column is a variable defined in ‘org.el’. > | Its value is -120 > | Original value was -77 > | > | You can customize this variable. > | > | Documentation: > | The column to which tags should be indented in a headline. > | If this number is positive, it specifies the column. If it is negative, > | it means that the tags should be flushright to that column. For example, > | -80 works well for a normal 80 character screen. > | When 0, place tags directly after headline text, with only one space in > | between. > ` Thanks Nick.
Re: Org mode for meeting minutes
*now -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.6-433-g4b2628
Re: New org-store-link on headlines contains tags
Hello, stardiviner writes: > Hi, Nicolas, I found the link part is fixed, Another itch is that the link > description part still contains the statistic cookie [1/2]. For example: > > #+begin_src org > * headline statistics [/] > > [[*headline statistics][headline statistics [/]]] > #+end_src OK. I removed it. Thank you. Regards, -- Nicolas Goaziou
Show full outline path when insert link
Hi all, When I am trying to store a link to an outline like this: “ * Headline 1 ** Headline 2 Point here. “ How can I automatically make it’s description to be “Headline 1/Headline 2” instead of just “Headline 2”? Best, Clive
Agenda: Default view missing 40th character
Hello all, I have had the 40th character missing from my agenda view, like this: Weeklytodo Expenses - Intern t and Friends :hab: habittodo [#A] Inbox, Check Calendars :hab: habittodo [#A] Unmount / Ba kup Notes Note how the 40th character is rendered as a space (the second line already has a space at the 40th character). Any ideas? Org mode version 9.2.5 (9.2.5-1-gff6508-elpa @ Emacs version 27.0.50 Thanks, --Nate
Re: Show full outline path when insert link
Something like (defun org-id-link-desk (link desk) "Description function for id: link." (let ((id (cadr (split-string link ":" (org-with-point-at (org-id-find id 'marker) (s-join "/" (org-get-outline-path 'with-self) (org-link-set-parameters "id" :desk #'org-id-link-desk) Best, Ihor Tung Clive writes: > Hi all, > > When I am trying to store a link to an outline like this: > “ > * Headline 1 > ** Headline 2 > Point here. > “ > How can I automatically make it’s description to be “Headline 1/Headline 2” > instead of just “Headline 2”? > > Best, > Clive -- Ihor Radchenko, PhD, Center for Advancing Materials Performance from the Nanoscale (CAMP-nano) State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China Email: yanta...@gmail.com, ihor_radche...@alumni.sutd.edu.sg
Re: Agenda: Default view missing 40th character
i presume you've already tried -Q, but do you have anything like a fill column marker package? yes, it is a long shot. On 3/24/20, Nathan Neff wrote: > Hello all, I have had the 40th character missing > from my agenda view, like this: > > Weeklytodo Expenses - Intern t and Friends > :hab: > habittodo [#A] Inbox, Check Calendars > :hab: > habittodo [#A] Unmount / Ba kup Notes > > Note how the 40th character is rendered as a space (the second > line already has a space at the 40th character). > > Any ideas? > Org mode version 9.2.5 (9.2.5-1-gff6508-elpa @ > Emacs version 27.0.50 > > Thanks, > --Nate > -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
Re: File Scoped Properties?
On Mon, Mar 9, 2020 at 9:24 AM Tim Visher wrote:
> On Fri, Mar 6, 2020 at 9:09 AM Tim Visher wrote:
>
>> Thanks for the response, Eric. :)
>>
>> On Fri, Mar 6, 2020 at 1:51 AM Fraga, Eric wrote:
>>
>>> On Thursday, 5 Mar 2020 at 10:28, Tim Visher wrote:
>>> > I _am_ able to get it to work by adding a file local variable like
>>> >
>>> > ```
>>> > # Local Variables:
>>> > # org-attach-id-dir: "~/.foo/data"
>>> > # End:
>>> > ```
>>> >
>>> > but then whenever I open the file it tells me it's possibly not safe
>>> to set
>>> > that.
>>>
>>> You've already received a more org-ish response but I'll give you an
>>> Emacs response to this part of your post: Emacs is simply making sure
>>> you are aware that a variable is being set when visiting a file.
>>>
>>
>> My question was more around why I had to do it at all since based on my
>> reading of the manual it seems like I should've been able to do this with
>> some kind of file-wide property. Specifically, I've never been able to wrap
>> my head around `(info "(org) Property Syntax")`.
>>
>> "Properties are key–value pairs. When they are associated with a single
>> entry or with a tree…," for instance, seems to imply by "When they are
>> associated with a single entry…" that they can be associated with all the
>> entries (or a particular tree or node).
>>
>> Anyway, I think between you and Gustav I finally have this sorted.
>>
>>1. To set properties at the top level of a file you need to use the
>>`#+PROPERTY: ` syntax. I've been trying to
>>figure out how I misinterpreted that in the past and I _think_ it was
>>because I assumed that the `#+PROPERTY` was actually `#+` as in
>>`#+DIR` rather than `#+PROPERTY: DIR`. It looks like to set a file local
>>property in an org file you _must_ (at least on 9.3 or earlier) use the
>>`#+PROPERTY: ` syntax.
>>
>>2. Even then by default org-attach property inheritance is set to
>>`'selective` and `org-use-property-inheritance` is set to off. I've now
>>customized `org-use-property-inheritance` to `'("DIR")` which I believe
>>says that I consider the `DIR` property to be a possible candidate for
>>inheritance and no others. I'm a little concerned about performance
>>implications as the manual gives me all kinds of scary warnings but we'll
>>see about that.
>>
>> Anyway this appears to work as I expect it to. I don't have to set a
>> file-local variable to anything. I'm using org properties. And
>> `org-attach-dir` now returns the proper directory for this file.
>>
>> Thanks all! If you think I'm still misunderstanding something please
>> correct me. :)
>>
>
> I'll go ahead and correct myself. (－‸ლ)
>
> It turns out that I wasn't understanding what the `DIR` property actually
> does. If `DIR` is set, it makes that the attachment directory, period. In
> other words it's different than the default `./data/` prefix directory in
> that ID paths are not then suffixed upon the end of it like
> `./data/XX/X-XXX-XXX/` for each entry. Instead, if you have `DIR` set,
> that headings attachment directory == `DIR`.
>
> So the way to change the attachment directory prefix is just not to mess
> with `DIR` at all. Instead, you must set the variable `org-attach-id-dir`,
> and if you want that to be local to a file the natural way to do that is
> with a file-local variable.
>
> ```
> # Local Variables:
> # org-attach-id-dir: "~/.foo/data"
> # End:
> ```
>
> Cheers. :)
>
This ended up producing more of a learning opportunity than I had initially
suspected and I wrote it up on my blog. In case anyone else is interested
in the details:
https://blog.twonegatives.com/post/613474532727095296/how-to-set-the-attach-directory-prefix-for
Happy Org!
