From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fletcher Charest Subject: Re: org-cook Date: Mon, 17 Mar 2014 15:22:50 +0100 Message-ID: References: <87mwgr4b2b.wl%egh@e6h.org> <87lhwb496i.wl%egh@e6h.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c1708287a32504f4ce270f Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53016) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPYRI-0004XT-Jt for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 10:22:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPYRH-0004Ye-0s for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 10:22:52 -0400 Received: from mail-qc0-x22a.google.com ([2607:f8b0:400d:c01::22a]:53334) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPYRG-0004YZ-Ra for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 10:22:50 -0400 Received: by mail-qc0-f170.google.com with SMTP id e9so6082176qcy.1 for ; Mon, 17 Mar 2014 07:22:50 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Robert Horn Cc: Erik Hetzner , Xebar Saram , org mode --001a11c1708287a32504f4ce270f Content-Type: text/plain; charset=ISO-8859-1 Hello everyone, Since we are on this subject, are you aware of any package that would make an 'automatic' shopping list based on recipes? My idea was to record recipes in this format: * Name of the recipe :tag: 1) Step one. 2) Step two. 3) Step three. :PROPERTIES: :ingredient_1: quantity :ingredient_2: quantity :ingredient_3: quantity :END: Tags could be anything, be mainly things like 'breakfast', 'main course' or 'dessert'. Then, with the point on the headline, (in the file buffer or in the agenda buffer), you could call a function that would add the ingredient to a list, or increment its quantity if the ingredient is already there. Maybe a function to add a random number of recipes (through a filter or not) to the shopping list would be nice too, if you don't know what to cook in a particular week. I'm planning to do this but my Elisp-fu is not great... Any tips of how implementing this? Are lists a good data structure for stocking the shopping list, before dumping it in a buffer? FC On Sun, Mar 16, 2014 at 1:40 AM, Robert Horn wrote: > I also use tables, and have one big recipe.org file. I considered > ingredient properties, etc., but ended up just text and find recipes by > using simple searches. They look like this: > > * Texas Skillet Corn Bread > > | Ingredient | Quantity | Instructions | > |------------------------+----------+-----------------| > | Bacon drippings or oil | 1/4 cup | | > | Yellow CornMeal | 1 cup | | > | All Purpose Flour | 1 cup | | > | Salt | 1/2 tsp | | > | Baking Power | 1 tsp | | > | Baking Soda | 1 tsp | | > | Sugar | 1 tbs | optional | > | Buttermilk | 1 cup | | > | Eggs | 2 | slightly beaten | > |------------------------+----------+-----------------| > > 1. Heat drippings in iron skillet > > 2. In large mixing bowl, mix cornmeal, flour, salt, baking x, and sugar. > > 3. Add buttermilk and stir rapidly. > > 4. Add eggs and mix > > 5. Add drippings > > 6. Pour into skillet, cover, and cook on low heat until lightly > browned and almost cooked through. > > > --001a11c1708287a32504f4ce270f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Since we are on this subject, are you aware of any package tha= t would make an 'automatic' shopping list based on recipes? My idea= was to record recipes in this format:

* Name of the recipe =A0 =A0 =A0=A0 =A0 :tag:

1) Step one.
2)= Step two.
3) Step three.

:PROPERTIES:
:ingredient_1: quantity=
:ingredi= ent_2: quantity
:ingredient_3= : quantity
:END:

Tags co= uld be anything, be mainly things like 'breakfast', 'main cours= e' or 'dessert'. Then, with the point on the headline, (in the = file buffer or in the agenda buffer), you could call a function that would = add the ingredient to a list, or increment its quantity if the ingredient i= s already there. Maybe a function to add a random number of recipes (throug= h a filter or not) to the shopping list would be nice too, if you don't= know what to cook in a particular week.

I&#= 39;m planning to do this but my Elisp-fu is not great... Any tips of how im= plementing this? Are lists a good data structure for stocking the shopping = list, before dumping it in a buffer?

FC<= br>


On Sun, Mar 16, 2014 at 1:40 AM, Robert Horn <= ;rjhorn@alum.mit.e= du> wrote:
I also use tables, and have one big recipe.org file. =A0I consider= ed
ingredient properties, etc., but ended up just text and find recipes by
using simple searches. =A0They look like this:

* Texas Skillet Corn Bread

| Ingredient =A0 =A0 =A0 =A0 =A0 =A0 | Quantity | Instructions =A0 =A0|
|------------------------+----------+-----------------|
| Bacon drippings or oil | 1/4 cup =A0| =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | | Yellow CornMeal =A0 =A0 =A0 =A0| 1 cup =A0 =A0| =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 |
| All Purpose Flour =A0 =A0 =A0| 1 cup =A0 =A0| =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 |
| Salt =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | 1/2 tsp =A0| =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 |
| Baking Power =A0 =A0 =A0 =A0 =A0 | 1 tsp =A0 =A0| =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 |
| Baking Soda =A0 =A0 =A0 =A0 =A0 =A0| 1 tsp =A0 =A0| =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 |
| Sugar =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| 1 tbs =A0 =A0| optional =A0 = =A0 =A0 =A0|
| Buttermilk =A0 =A0 =A0 =A0 =A0 =A0 | 1 cup =A0 =A0| =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 |
| Eggs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | 2 =A0 =A0 =A0 =A0| slightly be= aten |
|------------------------+----------+-----------------|

=A0 1. Heat drippings in iron skillet

=A0 2. In large mixing bowl, mix cornmeal, flour, salt, baking x, and sugar= .

=A0 3. Add buttermilk and stir rapidly.

=A0 4. Add eggs and mix

=A0 5. Add drippings

=A0 6. Pour into skillet, cover, and cook on low heat until lightly
=A0 =A0 =A0browned and almost cooked through.



--001a11c1708287a32504f4ce270f--