Re: [Orgmode] export and containers

2009-03-02 Thread Richard Riley
Sebastian Rose  writes:

> Richard Riley  writes:
>> It's been a while since I've looked at my org set up. One thing that
>> always struck me as a bit hacky was my use of
>>
>> :preamble "
>>
>> and the corresponding postamble to enclose the exported web pages into a
>> "container" div. Is there a better way to do this? I would think it
>> would be a common enough need that by default or via an option all html
>> should be enclosed in a "webcontainer" ID.
>
> While one container around everything makes it possible to center the
> page horizontally, two containers make it possible to center the page
> vertically as well.
>
> If we would go and change the structure once again, I'd even suggest the
> following:
>
> 
>-- center the page if desired
>  -- center the page if desired

Why always IDs as opposed to classes?

Can css selectors select based on a part of a name? If not then there is
no link between column-1 and column-2. e.g in this convention how does
one create a common style for all columns or all "sec-" objects?

>
>  -- Help with fixed TOC
> 
>   the toc
> 
>   
>
>  -- Help with fixed TOC
> All the rest of the content goes here
>   
>
>   
> postamble
>   
>
> 
>   
> 
>
>
>
> Having two boxes for the TOC would make the fixed TOC work in IE. In
> general, I prefere to use two kinds of Boxes:
>
>   - one for positioning, floating and so on. This one should have _no_
> padding or margin at all!

Can one not simply use .body for that?

>   - one for margin, padding, styling.
>
> I found, this is the only way to reliably enforce a layout across
> browsers.
>
>
> column-1 and column-2 are for that very reason. All we can do to put the
> TOC to the left or right is, to add margins to the body or the level 1
> contents, and place it there. This is, what causes the problems with the
> fixed TOC in IE. `column-1' and `column-2' (and `postamble') make it
> possible, to adjust the layout in various common ways.
>
> The `percent-50' (oh what a name) and `wrap' are just there, to be able
> to center the whole page horizontally _and_ veritcally.

>
>
> Best,
>
> --
> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
> Tel.:  +49 (0)511 - 36 58 472
> Fax:   +49 (0)1805 - 233633 - 11044
> mobil: +49 (0)173 - 83 93 417
> Http:  www.emma-stil.de
>

-- 
 important and urgent problems of the technology of today are no longer the 
satisfactions of the primary needs or of archetypal wishes, but the reparation 
of the evils and damages by the technology of yesterday.  ~Dennis Gabor, 
Innovations:  Scientific, Technological and Social, 1970


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Sebastian Rose
Richard Riley  writes:
> Sebastian Rose  writes:
>
>> Richard Riley  writes:
>>> It's been a while since I've looked at my org set up. One thing that
>>> always struck me as a bit hacky was my use of
>>>
>>> :preamble "
>>>
>>> and the corresponding postamble to enclose the exported web pages into a
>>> "container" div. Is there a better way to do this? I would think it
>>> would be a common enough need that by default or via an option all html
>>> should be enclosed in a "webcontainer" ID.
>>
>> While one container around everything makes it possible to center the
>> page horizontally, two containers make it possible to center the page
>> vertically as well.
>>
>> If we would go and change the structure once again, I'd even suggest the
>> following:
>>
>> 
>>-- center the page if desired
>>  -- center the page if desired
>
> Why always IDs as opposed to classes?


`percent-50' and `wrap' are there for a special purpose and unique in
that concern. `wrap' is the `content' you originally requested. I did
not use my brain and called it `wrap' without any annotation.

>>> :preamble "

I'd say they should have an ID assigned.



> Can css selectors select based on a part of a name? If not then there is
> no link between column-1 and column-2. e.g in this convention how does
> one create a common style for all columns or all "sec-" objects?

Aaah, OK, sorry for being unclear - a misunderstanding.

I did *not* mean to _change_ the structure of the XHTML in it's current
form, but simply _add_ additional containers to partition the whole
thing (just as you suggested) and thus make it possible to move certain
groups of content around through CSS.

All the "sec-" objects should go into `column-2'.
All the `sec-' objects share classes via the containers they live in:




etc.

That's already the case, and I think we don't need to change that.


* Suggestions for names

  `wrap' is, what they use in typolight and some other CMSs. But
  `content' sounds good to me too.

  


  

 ...

  

  

  2 Konfiguration 

  
   ...
  

... more sections, footnotes ...
  

  
postamble
  



  



>>
>>  -- Help with fixed TOC
>> 
>>   the toc
>> 
>>   
>>
>>  -- Help with fixed TOC
>> All the rest of the content goes here
>>   
>>
>>   
>> postamble
>>   
>>
>> 
>>   
>> 
>>
>>
>>
>> Having two boxes for the TOC would make the fixed TOC work in IE. In
>> general, I prefere to use two kinds of Boxes:
>>
>>   - one for positioning, floating and so on. This one should have _no_
>> padding or margin at all!
>
> Can one not simply use .body for that?
>
>>   - one for margin, padding, styling.
>>
>> I found, this is the only way to reliably enforce a layout across
>> browsers.
>>
>>
>> column-1 and column-2 are for that very reason. All we can do to put the
>> TOC to the left or right is, to add margins to the body or the level 1
>> contents, and place it there. This is, what causes the problems with the
>> fixed TOC in IE. `column-1' and `column-2' (and `postamble') make it
>> possible, to adjust the layout in various common ways.
>>
>> The `percent-50' (oh what a name) and `wrap' are just there, to be able
>> to center the whole page horizontally _and_ veritcally.
>
>>
>>
>> Best,
>>
>> --
>> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
>> Tel.:  +49 (0)511 - 36 58 472
>> Fax:   +49 (0)1805 - 233633 - 11044
>> mobil: +49 (0)173 - 83 93 417
>> Http:  www.emma-stil.de
>>

--
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.r...@emma-stil.de, sebastian_r...@gmx.de
Http:  www.emma-stil.de


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Carsten Dominik

Hi Sebastian,


On Mar 2, 2009, at 10:29 AM, Sebastian Rose wrote:


* Suggestions for names

 `wrap' is, what they use in typolight and some other CMSs. But
 `content' sounds good to me too.

 
   

 
   
...
   
 

 
   
 2  
Konfiguration 

 
  ...
 
   
   ... more sections, footnotes ...
 

 
   postamble
 


   
 



How about these names for additional divs

content-wrap
content ;; I think we should just have one around the entire  
content.
;; should this also contain the  with the page  
title?

;; I think yes

table-of-contents-wrap

footnote-wrap
bibliography-wrap
postamble-wrap

So we put all the stuff into specific "wrap" containers.
I don't so much like "column-1", because that looks fine
if you use it for columns, but it looks confusing if you
use it for something else...

- Carsten








-- Help with fixed TOC
   
 the toc
   
 

-- Help with fixed TOC
   All the rest of the content goes here
 

 
   postamble
 

   
 




Having two boxes for the TOC would make the fixed TOC work in IE. In
general, I prefere to use two kinds of Boxes:

 - one for positioning, floating and so on. This one should have  
_no_

   padding or margin at all!


Can one not simply use .body for that?


 - one for margin, padding, styling.

I found, this is the only way to reliably enforce a layout across
browsers.


column-1 and column-2 are for that very reason. All we can do to  
put the
TOC to the left or right is, to add margins to the body or the  
level 1
contents, and place it there. This is, what causes the problems  
with the

fixed TOC in IE. `column-1' and `column-2' (and `postamble') make it
possible, to adjust the layout in various common ways.

The `percent-50' (oh what a name) and `wrap' are just there, to be  
able

to center the whole page horizontally _and_ veritcally.





Best,

--
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449  
Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Http:  www.emma-stil.de



--
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449  
Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.r...@emma-stil.de, sebastian_r...@gmx.de
Http:  www.emma-stil.de


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode




___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] compiling org

2009-03-02 Thread Jörg Hagmann
I have been using the latest org versions on a mac and on ubuntu, 
updating according to instructions originally provided by Scott Randby 
(http://article.gmane.org/gmane.emacs.orgmode/7783/match=randby+hagmann+install).


It has always worked nicely, up to version 6.22trans. Since then it 
still works on the mac (where I have 6.23trans), but on ubuntu I'm stuck 
at 6.22trans (according to M-x org-version).


This is in my Makefile:

EMACS=/usr/bin/emacs
prefix=/usr/share
lispdir=$(prefix)/emacs/22.2/lisp

I have checked these locations, and there are no complaints when going 
through "make" and "make install"


I also tried installing the downloaded stable version (6.23b), with the 
same (i.e. no) result.


Any suggestions? Thanks, Jörg


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Sebastian Rose
Carsten Dominik  writes:
> Hi Sebastian,
>
>
> On Mar 2, 2009, at 10:29 AM, Sebastian Rose wrote:
>>
>> * Suggestions for names
>>
>>  `wrap' is, what they use in typolight and some other CMSs. But
>>  `content' sounds good to me too.
>>
>>  
>>
>>
>>  
>>
>> ...
>>
>>  
>>
>>  
>>
>>  2 Konfiguration
>> 
>>  
>>   ...
>>  
>>
>>... more sections, footnotes ...
>>  
>>
>>  
>>postamble
>>  
>>
>>
>>
>>  
>
>
> How about these names for additional divs
>
> content-wrap
> content ;; I think we should just have one around the entire content.
> ;; should this also contain the  with the page title?
> ;; I think yes

OK, one might be enough. There's a cross-browser CSS to center the contents
vertically with only one container:

#content-wrap
{
  ...
  margin-top:auto;
  margin-bottom:auto;
  vertical-align:middle;
  ...
}

And yes,  the title should be inside `content-wrap'

> table-of-contents-wrap
>
> footnote-wrap
> bibliography-wrap
> postamble-wrap
>
> So we put all the stuff into specific "wrap" containers.
> I don't so much like "column-1", because that looks fine
> if you use it for columns, but it looks confusing if you
> use it for something else...


Agreed.

How about `org(-container ?) for the outer most container? Think of
exporting the content only for inclusion into some framework. In that
case `org' seems a natural name.

Anyway, for sake of the TOC on the left, we should also wrap all the rest
of the contents in one  with postamble being the only exception.

The tree would simply be:

 org
title
table-of-contents-wrap
   table-of-contents
content-wrap
   sec-1...- unchanged
   footnotes   - unchanged
   bibliography
postamble// already there

The reason for the container around everything excluding title, TOC and
postamble is, that I don't want the TOC to live in the left margin of
the , the way it does now.

`float:left' for the TOC will cause the page to look funny in the most
cases: 

  +-+--+
  | TOC |  TITLE   |
  +-+  SEC-1   |
  |  SEC2  |
  |  SEC2  |
  |  FOOTNOTES |
  ++
  | POSTAMBLE  |
  ++

Better:

  +-+--+
  | TOC |  TITLE   |
  | |  SEC-1   |
  | |  SEC2|
  | |  SEC3|
  | |  FOOTNOTES   |
  ++
  | POSTAMBLE  |
  ++


And this one here would be nice (all navigational elements visible on
load): 

  +-+--+-+
  | TOC |  TITLE   | LOT |
  | |  SEC-1   +-+
  | |  SEC2| LOF |
  | |  SEC3+-+
  | |  FOOTNOTES   | BIB |
  +-+--+-+
  |POSTAMBLE |
  +--+

Some people (see drupal) put the postamble into the right/center column
for two and three column layout respectively. I don't like that very
much.




What we should do before we change anything, is to experiment with one
simple document and different stylesheets, to ensure everything works
the way we want it to.

I'll set up some with the different aproaches and try to add different
CSS stylesheets. Our aim must be to make many different layouts possible
(we will never make _all_ possible layouts feasable though).



Important layouts are:

  | Name| example  |
  |-+--|
  | Fixed TOC   | orgmode.org  |
  | Floating TOC| orgmode.org/worg |
  | Please add more here...|

  The usual page-flow will always stay what it is as long as no special
  styles are added.


Best,

   Sebastian


> - Carsten
>
>>
>>
>>
>>

 -- Help with fixed TOC

  the toc

  

 -- Help with fixed TOC
All the rest of the content goes here
  

  
postamble
  


  
 



 Having two boxes for the TOC would make the fixed TOC work in IE. In
 general, I prefere to use two kinds of Boxes:

  - one for positioning, floating and so on. This one should have _no_
padding or margin at all!
>>>
>>> Can one not simply use .body for that?
>>>
  - one for margin, padding, styling.

 I found, this is the only way to reliably enforce a layout across
 browsers.


 column-1 and column-2 are for that very reason. All we can do to put the
 TOC to the left or right is, to add margins to the body or the level 1
 contents, and place it there. This is, what causes the problems with the
 fixed TOC in IE. `column-1' and `column-2' (and `postamble') make it
 possible, to adjust the layout in various common ways.


Re: [Orgmode] export and containers

2009-03-02 Thread Carsten Dominik

OK, so I will wait with making changes until you have
done some experimentation, maybe put that up somewhere,
so that others can have a look?

- Carsten

On Mar 2, 2009, at 12:58 PM, Sebastian Rose wrote:


Carsten Dominik  writes:

Hi Sebastian,


On Mar 2, 2009, at 10:29 AM, Sebastian Rose wrote:


* Suggestions for names

`wrap' is, what they use in typolight and some other CMSs. But
`content' sounds good to me too.


  


  
   ...
  



  
2  
Konfiguration



 ...

  
  ... more sections, footnotes ...



  postamble



  




How about these names for additional divs

content-wrap
content ;; I think we should just have one around the  
entire content.
   ;; should this also contain the  with the page  
title?

   ;; I think yes


OK, one might be enough. There's a cross-browser CSS to center the  
contents

vertically with only one container:

#content-wrap
{
 ...
 margin-top:auto;
 margin-bottom:auto;
 vertical-align:middle;
 ...
}

And yes,  the title should be inside `content-wrap'


table-of-contents-wrap

footnote-wrap
bibliography-wrap
postamble-wrap

So we put all the stuff into specific "wrap" containers.
I don't so much like "column-1", because that looks fine
if you use it for columns, but it looks confusing if you
use it for something else...



Agreed.

How about `org(-container ?) for the outer most container? Think of
exporting the content only for inclusion into some framework. In that
case `org' seems a natural name.

Anyway, for sake of the TOC on the left, we should also wrap all the  
rest

of the contents in one  with postamble being the only exception.

The tree would simply be:

org
   title
   table-of-contents-wrap
  table-of-contents
   content-wrap
  sec-1...- unchanged
  footnotes   - unchanged
  bibliography
   postamble// already there

The reason for the container around everything excluding title, TOC  
and

postamble is, that I don't want the TOC to live in the left margin of
the , the way it does now.

`float:left' for the TOC will cause the page to look funny in the most
cases:

 +-+--+
 | TOC |  TITLE   |
 +-+  SEC-1   |
 |  SEC2  |
 |  SEC2  |
 |  FOOTNOTES |
 ++
 | POSTAMBLE  |
 ++

Better:

 +-+--+
 | TOC |  TITLE   |
 | |  SEC-1   |
 | |  SEC2|
 | |  SEC3|
 | |  FOOTNOTES   |
 ++
 | POSTAMBLE  |
 ++


And this one here would be nice (all navigational elements visible on
load):

 +-+--+-+
 | TOC |  TITLE   | LOT |
 | |  SEC-1   +-+
 | |  SEC2| LOF |
 | |  SEC3+-+
 | |  FOOTNOTES   | BIB |
 +-+--+-+
 |POSTAMBLE |
 +--+

Some people (see drupal) put the postamble into the right/center  
column

for two and three column layout respectively. I don't like that very
much.




What we should do before we change anything, is to experiment with one
simple document and different stylesheets, to ensure everything works
the way we want it to.

I'll set up some with the different aproaches and try to add different
CSS stylesheets. Our aim must be to make many different layouts  
possible

(we will never make _all_ possible layouts feasable though).



Important layouts are:

 | Name| example  |
 |-+--|
 | Fixed TOC   | orgmode.org  |
 | Floating TOC| orgmode.org/worg |
 | Please add more here...|

 The usual page-flow will always stay what it is as long as no special
 styles are added.


Best,

  Sebastian



- Carsten








   -- Help with fixed TOC
  
the toc
  


   -- Help with fixed TOC
  All the rest of the content goes here



  postamble


  





Having two boxes for the TOC would make the fixed TOC work in  
IE. In

general, I prefere to use two kinds of Boxes:

- one for positioning, floating and so on. This one should have  
_no_

  padding or margin at all!


Can one not simply use .body for that?


- one for margin, padding, styling.

I found, this is the only way to reliably enforce a layout across
browsers.


column-1 and column-2 are for that very reason. All we can do to  
put the
TOC to the left or right is, to add margins to the body or the  
level 1
contents, and place it there. This is, what causes the problems  
with the
fixed TOC in IE. `column-1' and `column-2' (and `postamble')  
make it

possible, to adjust the layout in various common ways.

The `percent-50' (oh what a name) and `wrap' are just there, to  
be able

to center the whole page horizontally _and_ veritcally.





Best,


--
Sebastian Rose, EMM

Re: [Orgmode] Re: MORE: Using git via USB for personal org dir and other data files

2009-03-02 Thread Alan

 [Thank you to Bernt for the *clear* explanation of using branches!]

 I seem to be moving out of the woods with this, and for the most
 part, the experiment has been going smoothly.  However, I've run
 afoul of permissions, a bugaboo that was mentioned in an earlier
 post on this topic.   

 I established a bare git repo on the USB drive, from a reasonably
 clean tree.  Pushing changes went well later on.  

 I cloned this repo onto the second machine, edited quite a bit,
 but was  dismayed when  I tried to push: an error message
 indicated that some file couldn't be written.  So far,  the
 problem seems to be permissions.  Preliminary checking shows that
 the group and user IDs are numerical on the flash drive,
 corresponding to the ID of the user who originally cloned the
 repo.  

 I have a tentative plan of action, but I know nothing about the
 use of permissions with git.  

1. I have established a group "git" with a high group number,
   so I can set create the same group on the work machine,
   with the same group number.  (I think it's too complicated
   to change user numbers at this point).  My users on the two
   machine have different user names.  It would be pretty
   complicated right now to change the user's ID number.

2. I am setting the group permissions as read and write.

   # chmod -R g+w /media/BLUE/org.git

3. Does this make sense?


 This is a great thing.  I want to put a whole bunch of work in such
 a repo.  

 Thank you for the help.  


  Alan 

  
-- 
Alan Davis

"An inviscid theory of flow renders the screw useless, but the need for
one non-existent."
---Lord Raleigh (John WilliamStrutt), or else his son, who was also a
   scientist.  


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Richard Riley
Sebastian Rose  writes:

> Richard Riley  writes:
>> Sebastian Rose  writes:
>>
>>> Richard Riley  writes:
 It's been a while since I've looked at my org set up. One thing that
 always struck me as a bit hacky was my use of

 :preamble "

 and the corresponding postamble to enclose the exported web pages into a
 "container" div. Is there a better way to do this? I would think it
 would be a common enough need that by default or via an option all html
 should be enclosed in a "webcontainer" ID.
>>>
>>> While one container around everything makes it possible to center the
>>> page horizontally, two containers make it possible to center the page
>>> vertically as well.
>>>
>>> If we would go and change the structure once again, I'd even suggest the
>>> following:
>>>
>>> 
>>>-- center the page if desired
>>>  -- center the page if desired
>>
>> Why always IDs as opposed to classes?
>
>
> `percent-50' and `wrap' are there for a special purpose and unique in
> that concern. `wrap' is the `content' you originally requested. I did
> not use my brain and called it `wrap' without any annotation.

"content" or "org-container". Wrap made no sense to me. It suggests word
wrap in the context. wrapper would be better. Purely vocabulary issue.

>
 :preamble "
>
> I'd say they should have an ID assigned.

Just an academic question : Why not a class?

>
>
>
>> Can css selectors select based on a part of a name? If not then there is
>> no link between column-1 and column-2. e.g in this convention how does
>> one create a common style for all columns or all "sec-" objects?
>
> Aaah, OK, sorry for being unclear - a misunderstanding.
>
> I did *not* mean to _change_ the structure of the XHTML in it's
> current

FYI I have abandoned xhtml in the smalle bit of web UI I touch.. It is
not cross platform/browser. Common concensus says make it html 4.01
strict compliant.


> form, but simply _add_ additional containers to partition the whole
> thing (just as you suggested) and thus make it possible to move certain
> groups of content around through CSS.
>
> All the "sec-" objects should go into `column-2'.

I dont know/understand what you mean with "columns".

Columns suggest layout in columns. It should simply be a "wrapper". That
wrapper may or may not be CSSd to a column. It might be a float or a
fixed position or .

> All the `sec-' objects share classes via the containers they live in:
>
> 
> 
>
> etc.

Yes. Thats what I was suggesting but see later on regarding css descendants.

>
> That's already the case, and I think we don't need to change that.
>

There is still this difference between ID and class name. I'm not sure I
see why.

>
> * Suggestions for names
>
>   `wrap' is, what they use in typolight and some other CMSs. But
>   `content' sounds good to me too.
>
>   
> 
>
>   
> 
>  ...
> 
>   
>
>   

where is the "base" class for box-2? 

The issue I see is that theres no way using this method to change all
"sec-" entries in an outline container for example since you cant use
css descendants since all have *unique* class names and IDs.

> 
>   2 
> Konfiguration 
>   

and another div here is what?


,
| >   
`

?


>...
>   
> 
> ... more sections, footnotes ...
>   
>
>   
> postamble
>   
>
>
> 
>   

I'm not sure I understand the need for the container container. Maybe I
need to Google up centering vertically. 

>
>
>
>>>
>>>  -- Help with fixed TOC
>>> 
>>>   the toc
>>> 
>>>   
>>>
>>>  -- Help with fixed TOC
>>> All the rest of the content goes here
>>>   
>>>
>>>   
>>> postamble
>>>   
>>>
>>> 
>>>   
>>> 
>>>
>>>
>>>
>>> Having two boxes for the TOC would make the fixed TOC work in IE. In
>>> general, I prefere to use two kinds of Boxes:
>>>
>>>   - one for positioning, floating and so on. This one should have _no_
>>> padding or margin at all!
>>
>> Can one not simply use .body for that?
>>
>>>   - one for margin, padding, styling.
>>>
>>> I found, this is the only way to reliably enforce a layout across
>>> browsers.
>>>
>>>
>>> column-1 and column-2 are for that very reason. All we can do to put the
>>> TOC to the left or right is, to add margins to the body or the level 1
>>> contents, and place it there. This is, what causes the problems with the
>>> fixed TOC in IE. `column-1' and `column-2' (and `postamble') make it
>>> possible, to adjust the layout in various common ways.
>>>
>>> The `percent-50' (oh what a name) and `wrap' are just there, to be able
>>> to center the whole page horizontally _and_ veritcally.
>>
>>>
>>>
>>> Best,
>>>
>>> --
>>> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
>>> Tel.:  +49 (0)511 - 36 58 472
>>> Fax:   +49 (0)1805 - 233633 - 11044
>>> mobil: +

Re: [Orgmode] Re: MORE: Using git via USB for personal org dir and other data files

2009-03-02 Thread Bernt Hansen
Changing the permissions and using a group shouldn't be necessary.

If you're using Linux to mount the usb stick the 'user' option makes all
of the files on the drive owned by the person that mounts it.

,[ /etc/fstab ]
| /dev/sdb1 /usb vfat defaults,user,noauto,shortname=mixed 0 0
`

Then it just works :)

-Bernt

Alan   writes:

>  [Thank you to Bernt for the *clear* explanation of using branches!]
>
>  I seem to be moving out of the woods with this, and for the most
>  part, the experiment has been going smoothly.  However, I've run
>  afoul of permissions, a bugaboo that was mentioned in an earlier
>  post on this topic.   
>
>  I established a bare git repo on the USB drive, from a reasonably
>  clean tree.  Pushing changes went well later on.  
>
>  I cloned this repo onto the second machine, edited quite a bit,
>  but was  dismayed when  I tried to push: an error message
>  indicated that some file couldn't be written.  So far,  the
>  problem seems to be permissions.  Preliminary checking shows that
>  the group and user IDs are numerical on the flash drive,
>  corresponding to the ID of the user who originally cloned the
>  repo.  
>
>  I have a tentative plan of action, but I know nothing about the
>  use of permissions with git.  
>
> 1. I have established a group "git" with a high group number,
>so I can set create the same group on the work machine,
>with the same group number.  (I think it's too complicated
>to change user numbers at this point).  My users on the two
>machine have different user names.  It would be pretty
>complicated right now to change the user's ID number.
>
> 2. I am setting the group permissions as read and write.
>
>  # chmod -R g+w /media/BLUE/org.git
>
> 3. Does this make sense?
>
>
>  This is a great thing.  I want to put a whole bunch of work in such
>  a repo.  
>
>  Thank you for the help.  
>
>
>   Alan 
>
>   
> -- 
> Alan Davis
>
> "An inviscid theory of flow renders the screw useless, but the need for
> one non-existent."
> ---Lord Raleigh (John WilliamStrutt), or else his son, who was also a
>scientist.  


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Sebastian Rose

OK - I failed badly :-(

I think we can skip the extra  element around the TOC. 

Here's why:

  As it looks now, the problem with the fixed TOC does not go away. My
  old trick seems to work only for HTML doctype and/or tables...  Should
  have tested that one before...

  So until now it's not getting any better - but more complicated.

  And all those stlyes in the stylesheet become confusing :-/

  The main problem is the height of the TOC on orgmode.org. The 
  element grows and shrinks in height when we resize the window.
  Unfortunately, we can't set the height property to 100% because of the
  unicorn. Instead I set it to 60% to support Netbooks - but 60% will be
  too high if the window is resized to be under a certain height. And
  60% is low, if the window fills a bigger screen (> 17')

  Seems I can't solve that by adding structural elements. The only
  element I could think of would be a table with height=100% and the
  unicorn in the first row (fixed height), TOC in the second row (no
  height property).


Most of this seems to be true for the other containers I thought of.


Just one around everything and one around the all the sections and
footnotes seems to make sense so far.




Maybe someone finds another way of `skinning' the XHTML output in the
future. 



How about adding custom HTML before and after writing the main
containers?

Can't we something like this here ? :

   (defun my-export-add-custom-html(when, which)
  "when is either 'before' or 'after', which is one of:
- 'body'
- 'title'
- 'toc'
- 'contents'
- 'lot'
   ..."
 (when (string= "body" which)
(if (string= "before" when)
  "")
  "")
   )


In org-publish-project-alist:

   :custom-html-funcion   my-export-add-custom-html

and perhaps:

   :org-export-html-sequence '("title" "toc" "content" "footnotes")
   ;; getting wild and offtopic:
   :custom-id-function   my-org-id-was-found


That way the output would win flexibility and get closer to an generic
export. One could implement a table based layout, or reuse containers
from the CMS the pages should be used in.  Not to forget `' or similar.

We would lose the guaranty that anything validates or org-info.js works
with the resulting structure though. But we could provide different
`themes' on Worg which are guarantied to work (and enhanced by the
comunity).


Or is all this completely weired?




Best,

  Sebastian



Carsten Dominik  writes:
> OK, so I will wait with making changes until you have
> done some experimentation, maybe put that up somewhere,
> so that others can have a look?



>
> - Carsten
>
> On Mar 2, 2009, at 12:58 PM, Sebastian Rose wrote:
>
>> Carsten Dominik  writes:
>>> Hi Sebastian,
>>>
>>>
>>> On Mar 2, 2009, at 10:29 AM, Sebastian Rose wrote:

 * Suggestions for names

 `wrap' is, what they use in typolight and some other CMSs. But
 `content' sounds good to me too.

 
   

 
   
...
   
 

 
   
 2 
 Konfiguration
 
 
  ...
 
   
   ... more sections, footnotes ...
 

 
   postamble
 


   
 
>>>
>>>
>>> How about these names for additional divs
>>>
>>> content-wrap
>>> content ;; I think we should just have one around the entire 
>>> content.
>>>;; should this also contain the  with the page title?
>>>;; I think yes
>>
>> OK, one might be enough. There's a cross-browser CSS to center the contents
>> vertically with only one container:
>>
>> #content-wrap
>> {
>>  ...
>>  margin-top:auto;
>>  margin-bottom:auto;
>>  vertical-align:middle;
>>  ...
>> }
>>
>> And yes,  the title should be inside `content-wrap'
>>
>>> table-of-contents-wrap
>>>
>>> footnote-wrap
>>> bibliography-wrap
>>> postamble-wrap
>>>
>>> So we put all the stuff into specific "wrap" containers.
>>> I don't so much like "column-1", because that looks fine
>>> if you use it for columns, but it looks confusing if you
>>> use it for something else...
>>
>>
>> Agreed.
>>
>> How about `org(-container ?) for the outer most container? Think of
>> exporting the content only for inclusion into some framework. In that
>> case `org' seems a natural name.
>>
>> Anyway, for sake of the TOC on the left, we should also wrap all the rest
>> of the contents in one  with postamble being the only exception.
>>
>> The tree would simply be:
>>
>> org
>>title
>>table-of-contents-wrap
>>   table-of-contents
>>content-wrap
>>   sec-1...- unchanged
>>   footnotes   - unchanged
>>   bibliography
>>postamble// already there
>>
>> The reason for the container around everything excluding title, TOC and
>> postamble is, that I don't want the TOC to live in the left margin of
>> the , the way it does now.
>>
>> `float:left' for the TOC will

Re: [Orgmode] org-exp-bibtex.el - add support to citing bibtex in both html and latex exports

2009-03-02 Thread William Henney
Hi Taru

On Sun, Mar 1, 2009 at 4:57 AM, Taru Karttunen  wrote:
> Selecting only some entries to display would be possible,
> but is it really necessary? In my use cases I just tend
> to have a per-article bib-file that contains the entries
> I wish to use. Making a rich enough API to sort, reformat
> and select a portion of a BibTeX file seems quite overblown
> for org.

Personally, I use a single .bib file for everything, which is
currently running at 12269 entries, so something like Carsten's
suggestion would be necessary before org-exp-bibtex.el became useful
to me :)

Bibtex2html already comes with a separate tool "bib2bib" which seems
to already do exactly what is needed. See
http://www.lri.fr/~filliatr/bibtex2html/doc/#htoc12

Cheers

Will


-- 

  Dr William Henney, Centro de Radioastronomía y Astrofísica,
  Universidad Nacional Autónoma de México, Campus Morelia


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Sebastian Rose
Richard Riley  writes:
> Sebastian Rose  writes:
>
>> Richard Riley  writes:
>>> Sebastian Rose  writes:
>>>
 Richard Riley  writes:
> It's been a while since I've looked at my org set up. One thing that
> always struck me as a bit hacky was my use of
>
> :preamble "
>
> and the corresponding postamble to enclose the exported web pages into a
> "container" div. Is there a better way to do this? I would think it
> would be a common enough need that by default or via an option all html
> should be enclosed in a "webcontainer" ID.

 While one container around everything makes it possible to center the
 page horizontally, two containers make it possible to center the page
 vertically as well.

 If we would go and change the structure once again, I'd even suggest the
 following:

 
-- center the page if desired
  -- center the page if desired
>>>
>>> Why always IDs as opposed to classes?
>>
>>
>> `percent-50' and `wrap' are there for a special purpose and unique in
>> that concern. `wrap' is the `content' you originally requested. I did
>> not use my brain and called it `wrap' without any annotation.
>
> "content" or "org-container". Wrap made no sense to me. It suggests word
> wrap in the context. wrapper would be better. Purely vocabulary issue.
>
>>
> :preamble "
>>
>> I'd say they should have an ID assigned.
>
> Just an academic question : Why not a class?



Because it's supposed to be the exact entity, that contains exact all
the other stuff and shares no styles but those all  elements and
 share. A user could add another container ""
and break the page layout.

But as no browser seems to force the uniquety of IDs, it doesn't yet
make a difference really.




>>> Can css selectors select based on a part of a name? If not then there is
>>> no link between column-1 and column-2. e.g in this convention how does
>>> one create a common style for all columns or all "sec-" objects?
>>
>> Aaah, OK, sorry for being unclear - a misunderstanding.
>>
>> I did *not* mean to _change_ the structure of the XHTML in it's
>> current
>
> FYI I have abandoned xhtml in the smalle bit of web UI I touch.. It is
> not cross platform/browser. Common concensus says make it html 4.01
> strict compliant.



I can't tell that, and I touch quite some UIs. XHTML is more rigid
though. Case sensitive and so on. It's what WEB-programming always was:
fiddling with different browsers, each of which having it's own
`standard' and finding the Lowest Common Denominator...
It doesn't really have to do anything with programming, where things
usually are well defined even accross different plattforms.

But I can say, that XHTML is just as crossbrowser as HTML. Validating
helps a lot though. 


>> form, but simply _add_ additional containers to partition the whole
>> thing (just as you suggested) and thus make it possible to move certain
>> groups of content around through CSS.
>>
>> All the "sec-" objects should go into `column-2'.
>
> I dont know/understand what you mean with "columns".
>
> Columns suggest layout in columns. It should simply be a "wrapper". That
> wrapper may or may not be CSSd to a column. It might be a float or a
> fixed position or .


Yes, sorry - those where stupid names...


>> All the `sec-' objects share classes via the containers they live in:
>>
>> 
>> 
>>
>> etc.
>
> Yes. Thats what I was suggesting but see later on regarding css descendants.
>
>>
>> That's already the case, and I think we don't need to change that.
>>
>
> There is still this difference between ID and class name. I'm not sure I
> see why.


Hmm - let's see...

Each of the elements has a class assigned, that is common to those on
the same level.

Some of them have an additional ID that makes it possible to address
exactly that very element:


4.1 Pi 


The headline `PI' is no different from other headlines in the document
from JavaScript's or XML-Tools point of view. What makes the element
special, is just it's ID.

There could be a headline `PI' on the same level in any other Section of
the document. That's why we need the ID.

Sure you may use CSS-selectors like this, to style all the level 3 
elements:

.outline-text-3 p
{
  color:green;
}





>>
>> * Suggestions for names
>>
>>   `wrap' is, what they use in typolight and some other CMSs. But
>>   `content' sounds good to me too.
>>
>>   
>> 
>>
>>   
>> 
>>  ...
>> 
>>   
>>
>>   
>
> where is the "base" class for box-2?
>
> The issue I see is that theres no way using this method to change all
> "sec-" entries in an outline container for example since you cant use
> css descendants since all have *unique* class names and IDs.


Hihi, I just see what you mean (below). I seem to have no luck in
answering your mails ;-)

In this example below it seems that `outline-2' has the `2' in it's class
name, because it's the class of the conta

Re: [Orgmode] export and containers

2009-03-02 Thread Carsten Dominik


On Mar 2, 2009, at 5:00 PM, Sebastian Rose wrote:



OK - I failed badly :-(

I think we can skip the extra  element around the TOC.

Here's why:

 As it looks now, the problem with the fixed TOC does not go away. My
 old trick seems to work only for HTML doctype and/or tables...   
Should

 have tested that one before...

 So until now it's not getting any better - but more complicated.

 And all those stlyes in the stylesheet become confusing :-/

 The main problem is the height of the TOC on orgmode.org. The 
 element grows and shrinks in height when we resize the window.
 Unfortunately, we can't set the height property to 100% because of  
the
 unicorn. Instead I set it to 60% to support Netbooks - but 60% will  
be

 too high if the window is resized to be under a certain height. And
 60% is low, if the window fills a bigger screen (> 17')

 Seems I can't solve that by adding structural elements. The only
 element I could think of would be a table with height=100% and the
 unicorn in the first row (fixed height), TOC in the second row (no
 height property).


Most of this seems to be true for the other containers I thought of.


Just one around everything and one around the all the sections and
footnotes seems to make sense so far.



So one that wraps everything in body.  OK, let's call it "content".

And then one that does contains the sections and footnotes, but
not the title, preamble, and postamble?  Am I understanding this
correctly?

- Carsten










Maybe someone finds another way of `skinning' the XHTML output in the
future.



How about adding custom HTML before and after writing the main
containers?

Can't we something like this here ? :

  (defun my-export-add-custom-html(when, which)
 "when is either 'before' or 'after', which is one of:
   - 'body'
   - 'title'
   - 'toc'
   - 'contents'
   - 'lot'
  ..."
(when (string= "body" which)
   (if (string= "before" when)
 "")
 "")
  )


In org-publish-project-alist:

  :custom-html-funcion   my-export-add-custom-html

and perhaps:

  :org-export-html-sequence '("title" "toc" "content" "footnotes")
  ;; getting wild and offtopic:
  :custom-id-function   my-org-id-was-found


That way the output would win flexibility and get closer to an generic
export. One could implement a table based layout, or reuse containers
from the CMS the pages should be used in.  Not to forget `' or similar.

We would lose the guaranty that anything validates or org-info.js  
works

with the resulting structure though. But we could provide different
`themes' on Worg which are guarantied to work (and enhanced by the
comunity).


Or is all this completely weired?




Best,

 Sebastian



Carsten Dominik  writes:

OK, so I will wait with making changes until you have
done some experimentation, maybe put that up somewhere,
so that others can have a look?






- Carsten

On Mar 2, 2009, at 12:58 PM, Sebastian Rose wrote:


Carsten Dominik  writes:

Hi Sebastian,


On Mar 2, 2009, at 10:29 AM, Sebastian Rose wrote:


* Suggestions for names

`wrap' is, what they use in typolight and some other CMSs. But
`content' sounds good to me too.


 

   
 
  ...
 
   

   
 
   2  
Konfiguration


   
...
   
 
 ... more sections, footnotes ...
   

   
 postamble
   


 




How about these names for additional divs

content-wrap
content ;; I think we should just have one around the  
entire content.
  ;; should this also contain the  with the page  
title?

  ;; I think yes


OK, one might be enough. There's a cross-browser CSS to center the  
contents

vertically with only one container:

#content-wrap
{
...
margin-top:auto;
margin-bottom:auto;
vertical-align:middle;
...
}

And yes,  the title should be inside `content-wrap'


table-of-contents-wrap

footnote-wrap
bibliography-wrap
postamble-wrap

So we put all the stuff into specific "wrap" containers.
I don't so much like "column-1", because that looks fine
if you use it for columns, but it looks confusing if you
use it for something else...



Agreed.

How about `org(-container ?) for the outer most container? Think of
exporting the content only for inclusion into some framework. In  
that

case `org' seems a natural name.

Anyway, for sake of the TOC on the left, we should also wrap all  
the rest
of the contents in one  with postamble being the only  
exception.


The tree would simply be:

org
  title
  table-of-contents-wrap
 table-of-contents
  content-wrap
 sec-1...- unchanged
 footnotes   - unchanged
 bibliography
  postamble// already there

The reason for the container around everything excluding title,  
TOC and
postamble is, that I don't want the TOC to live in the left margin  
of

the , the way it does now.

`float:left' for the TOC will cause the page to look funny in the  
most

cases:

+-+--+
| TOC |  TITLE   |
+-+  SEC-1   |
|

[Orgmode] Switching between many contexts

2009-03-02 Thread Daniel Clemente

  Hi. I have this scenario: I track several projects in a single file, each in 
its own level-1 section, but each week I'm working only on one project.
  In my agenda (C-a a) I'm currently seeing scheduled tasks from all projects, 
and I would like to exclude all projects but one.
  I recently added a CATEGORY property to each section.


  My questions are:

1. How can I exclude a category from the agenda view?
   Probably with key \ TAB CATEGORY="something", but I can't make it work and 
I'm confused by the many types of searches that are referred to in the manual.

2. How can I create an agenda view that looks like the normal agenda, but 
ignores some categories? (at least on that file).

3. Do you implement this scenario in other ways? For instance, one can add the 
COMMENT keyword the unwanted projects, use different files, close all old tasks 
after each context switch, use other tags, …


  Thanks,
Daniel



___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Richard Riley
Carsten Dominik  writes:

> On Mar 2, 2009, at 5:00 PM, Sebastian Rose wrote:
>
>>
>> OK - I failed badly :-(
>>
>> I think we can skip the extra  element around the TOC.
>>
>> Here's why:
>>
>>  As it looks now, the problem with the fixed TOC does not go away. My
>>  old trick seems to work only for HTML doctype and/or tables...
>> Should
>>  have tested that one before...
>>
>>  So until now it's not getting any better - but more complicated.
>>
>>  And all those stlyes in the stylesheet become confusing :-/
>>
>>  The main problem is the height of the TOC on orgmode.org. The 
>>  element grows and shrinks in height when we resize the window.
>>  Unfortunately, we can't set the height property to 100% because of
>> the
>>  unicorn. Instead I set it to 60% to support Netbooks - but 60% will
>> be
>>  too high if the window is resized to be under a certain height. And
>>  60% is low, if the window fills a bigger screen (> 17')
>>
>>  Seems I can't solve that by adding structural elements. The only
>>  element I could think of would be a table with height=100% and the
>>  unicorn in the first row (fixed height), TOC in the second row (no
>>  height property).
>>
>>
>> Most of this seems to be true for the other containers I thought of.
>>
>>
>> Just one around everything and one around the all the sections and
>> footnotes seems to make sense so far.
>
>
> So one that wraps everything in body.  OK, let's call it "content".
>
> And then one that does contains the sections and footnotes, but
> not the title, preamble, and postamble?  Am I understanding this
> correctly?
>
> - Carsten

So long as every thing has a div we can then use descendants of the main
content to CSS any elements.

I see the most important thing (and making it simple) is just to assign
a class ID at the org file level

#class=myclass
..stuff
#endclass

This generates


..stuff


at html export and whatever for anything else.

I really dont see the plethora of sec-id# that are currently generated
being really useful since they change on each export if new stuff is
entered. This make existing CSS redundant unfortunately.

Sebastian?


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Switching between many contexts

2009-03-02 Thread Samuel Wales
I've been wondering about something similar.  Suppose you have a bunch
of important tasks and a bunch of fluff tasks.  It might be useful to
be able to have the "agenda" item in org-agenda-custom-commands accept
a tags search so that you can use :fluff: on the fluff tasks and
assign a key for everything except :fluff: tasks.  I was going to wait
until after the Lisp syntax for searches was implemented and for me to
get more experience before suggesting it.  In any case, it looks like
the same kind of thing with categories?

On Mon, Mar 2, 2009 at 11:03, Daniel Clemente  wrote:
>
>  Hi. I have this scenario: I track several projects in a single file, each in 
> its own level-1 section, but each week I'm working only on one project.
>  In my agenda (C-a a) I'm currently seeing scheduled tasks from all projects, 
> and I would like to exclude all projects but one.
>  I recently added a CATEGORY property to each section.
>
>
>  My questions are:
>
> 1. How can I exclude a category from the agenda view?
>   Probably with key \ TAB CATEGORY="something", but I can't make it work and 
> I'm confused by the many types of searches that are referred to in the manual.
>
> 2. How can I create an agenda view that looks like the normal agenda, but 
> ignores some categories? (at least on that file).
>
> 3. Do you implement this scenario in other ways? For instance, one can add 
> the COMMENT keyword the unwanted projects, use different files, close all old 
> tasks after each context switch, use other tags, …
>
>
>  Thanks,
> Daniel
>
>
>
> ___
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>



-- 
Myalgic encephalomyelitis denialism is causing death (decades early;
Jason et al. 2006) and severe suffering, pain, and disability (worse
than nearly all other serious diseases studied; Schweitzer et al.
1995) and grossly corrupting science.  The denialism is worse than it
ever was with even AIDS or MS.
http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: Switching between many contexts

2009-03-02 Thread Bernt Hansen
Hi Daniel,



Daniel Clemente  writes:

>   Hi. I have this scenario: I track several projects in a single file,
>   each in its own level-1 section, but each week I'm working only on
>   one project.  In my agenda (C-a a) I'm currently seeing scheduled
>   tasks from all projects, and I would like to exclude all projects
>   but one.  I recently added a CATEGORY property to each section.
>
>
>   My questions are:
>
> 1. How can I exclude a category from the agenda view?  Probably with
> key \ TAB CATEGORY="something", but I can't make it work and I'm
> confused by the many types of searches that are referred to in the
> manual.

I use tags instead of categories for filtering.  Categories for me are
only displayed in the agenda as extra information for what the task
belongs to.

Since tags are inherited you can just add a tag to the level 1 task and
then filter using that tag.

> >
> 2. How can I create an agenda view that looks like the normal agenda,
> but ignores some categories? (at least on that file).

Using tags instead of categories:

Do a normal agenda view and then limit with / TAB tag-names-goes-here or
use one of your fast key selections for tags.  (/ key)

You can use a filter to remove tasks with a specific tag

C-c a t / - TAB PROJ1 RET

will display all TODO tasks and then remove any tasks with the PROJ1
tag.  You can repeat the /- TAB tagname sequence to remove multiple
projects.

For my standard tags I have quick keys defined in my org-tag-alist so I
can just use those to filter tasks.  That works great!

> >
> 3. Do you implement this scenario in other ways? For instance, one can
> add the COMMENT keyword the unwanted projects, use different files,
> close all old tasks after each context switch, use other tags, …

I split projects into separate files and add a #+FILETAGS: at the top.
For instance my org.org file has
#+FILETAGS: ORG

and all tasks in that file get the ORG tag.

For clients I create one or more files and use a FILETAGS setting to
create a tag for that client - then I can limit the agenda to just that
client quickly.  Some clients have multiple project files (one of my
clients has client systems which I work on so each system has its own
org file but I can view everything for that client by limiting to the
client tag)

I find limiting the agenda with tag filters very quick and effective.

HTH,
Bernt




___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: Switching between many contexts

2009-03-02 Thread Bernt Hansen
Assign a FLUFF tag to your tasks then run the agenda normally and remove
the fluff with

/ - TAB FLUFF RET

or if you do that often set up org-tags-alist with F for FLUFF and just

/ - F

-Bernt


Samuel Wales  writes:

> I've been wondering about something similar.  Suppose you have a bunch
> of important tasks and a bunch of fluff tasks.  It might be useful to
> be able to have the "agenda" item in org-agenda-custom-commands accept
> a tags search so that you can use :fluff: on the fluff tasks and
> assign a key for everything except :fluff: tasks.  I was going to wait
> until after the Lisp syntax for searches was implemented and for me to
> get more experience before suggesting it.  In any case, it looks like
> the same kind of thing with categories?
>
> On Mon, Mar 2, 2009 at 11:03, Daniel Clemente  wrote:
>>
>>  Hi. I have this scenario: I track several projects in a single file, each 
>> in its own level-1 section, but each week I'm working only on one project.
>>  In my agenda (C-a a) I'm currently seeing scheduled tasks from all 
>> projects, and I would like to exclude all projects but one.
>>  I recently added a CATEGORY property to each section.
>>
>>
>>  My questions are:
>>
>> 1. How can I exclude a category from the agenda view?
>>   Probably with key \ TAB CATEGORY="something", but I can't make it work and 
>> I'm confused by the many types of searches that are referred to in the 
>> manual.
>>
>> 2. How can I create an agenda view that looks like the normal agenda, but 
>> ignores some categories? (at least on that file).
>>
>> 3. Do you implement this scenario in other ways? For instance, one can add 
>> the COMMENT keyword the unwanted projects, use different files, close all 
>> old tasks after each context switch, use other tags, …
>>
>>
>>  Thanks,
>> Daniel
>>
>>
>>
>> ___
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>
>
>
> -- 
> Myalgic encephalomyelitis denialism is causing death (decades early;
> Jason et al. 2006) and severe suffering, pain, and disability (worse
> than nearly all other serious diseases studied; Schweitzer et al.
> 1995) and grossly corrupting science.  The denialism is worse than it
> ever was with even AIDS or MS.
> http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm
>
>
> ___
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Sebastian Rose


Carsten Dominik  writes:
> On Mar 2, 2009, at 5:00 PM, Sebastian Rose wrote:
>
>>
>> OK - I failed badly :-(
>>
>> I think we can skip the extra  element around the TOC.
>>
>> Here's why:
>>
>>  As it looks now, the problem with the fixed TOC does not go away. My
>>  old trick seems to work only for HTML doctype and/or tables...  Should
>>  have tested that one before...
>>
>>  So until now it's not getting any better - but more complicated.
>>
>>  And all those stlyes in the stylesheet become confusing :-/
>>
>>  The main problem is the height of the TOC on orgmode.org. The 
>>  element grows and shrinks in height when we resize the window.
>>  Unfortunately, we can't set the height property to 100% because of the
>>  unicorn. Instead I set it to 60% to support Netbooks - but 60% will be
>>  too high if the window is resized to be under a certain height. And
>>  60% is low, if the window fills a bigger screen (> 17')
>>
>>  Seems I can't solve that by adding structural elements. The only
>>  element I could think of would be a table with height=100% and the
>>  unicorn in the first row (fixed height), TOC in the second row (no
>>  height property).
>>
>>
>> Most of this seems to be true for the other containers I thought of.
>>
>>
>> Just one around everything and one around the all the sections and
>> footnotes seems to make sense so far.
>
>
> So one that wraps everything in body.  OK, let's call it "content".
>
> And then one that does contains the sections and footnotes, but
> not the title, preamble, and postamble?  Am I understanding this
> correctly?


Just the outer one then. As long as noone uses an container we shouldn't
add it.

Even the inner one with all the sections is merely a matter of taste.

What do you think about the hook idea in my previous mail? Was that to
weired? It thought that would make complex layouts possible without
poluting the *.org sources with things like

  @

and would keep org-exp.el simple too.


Best,

  Sebastian


> - Carsten
>
>
>
>
>>
>>
>>
>>
>>
>> Maybe someone finds another way of `skinning' the XHTML output in the
>> future.
>>
>>
>>
>> How about adding custom HTML before and after writing the main
>> containers?
>>
>> Can't we something like this here ? :
>>
>>   (defun my-export-add-custom-html(when, which)
>>  "when is either 'before' or 'after', which is one of:
>>- 'body'
>>- 'title'
>>- 'toc'
>>- 'contents'
>>- 'lot'
>>   ..."
>> (when (string= "body" which)
>>(if (string= "before" when)
>>  "")
>>  "")
>>   )
>>
>>
>> In org-publish-project-alist:
>>
>>   :custom-html-funcion   my-export-add-custom-html
>>
>> and perhaps:
>>
>>   :org-export-html-sequence '("title" "toc" "content" "footnotes")
>>   ;; getting wild and offtopic:
>>   :custom-id-function   my-org-id-was-found
>>
>>
>> That way the output would win flexibility and get closer to an generic
>> export. One could implement a table based layout, or reuse containers
>> from the CMS the pages should be used in.  Not to forget `> . ?>' or similar.
>>
>> We would lose the guaranty that anything validates or org-info.js works
>> with the resulting structure though. But we could provide different
>> `themes' on Worg which are guarantied to work (and enhanced by the
>> comunity).
>>
>>
>> Or is all this completely weired?
>>
>>
>>
>>
>> Best,
>>
>>  Sebastian
>>
>>
>>
>> Carsten Dominik  writes:
>>> OK, so I will wait with making changes until you have
>>> done some experimentation, maybe put that up somewhere,
>>> so that others can have a look?
>>
>>
>>
>>>
>>> - Carsten
>>>
>>> On Mar 2, 2009, at 12:58 PM, Sebastian Rose wrote:
>>>
 Carsten Dominik  writes:
> Hi Sebastian,
>
>
> On Mar 2, 2009, at 10:29 AM, Sebastian Rose wrote:
>>
>> * Suggestions for names
>>
>> `wrap' is, what they use in typolight and some other CMSs. But
>> `content' sounds good to me too.
>>
>> 
>>  
>>
>>
>>  
>>   ...
>>  
>>
>>
>>
>>  
>>2
>> Konfiguration
>> 
>>
>> ...
>>
>>  
>>  ... more sections, footnotes ...
>>
>>
>>
>>  postamble
>>
>>
>>
>>  
>> 
>
>
> How about these names for additional divs
>
> content-wrap
> content ;; I think we should just have one around the entire
> content.
>   ;; should this also contain the  with the page title?
>   ;; I think yes

 OK, one might be enough. There's a cross-browser CSS to center the contents
 vertically with only one container:

 #content-wrap
 {
 ...
 margin-top:auto;
 margin-bottom:auto;
 vertical-align:middle;
 ...
 }

 And yes,  the title should be inside `content-wrap'

> table-of-contents-wrap
>
> footnote-w

Re: [Orgmode] export and containers

2009-03-02 Thread Sebastian Rose
Richard Riley  writes:
> I really dont see the plethora of sec-id# that are currently generated
> being really useful since they change on each export if new stuff is
> entered. This make existing CSS redundant unfortunately.

The IDs in the section headings are not meant for CSS styling. That's
what the classes are for.


Regards,

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Http:  www.emma-stil.de


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Sebastian Rose
Richard Riley  writes:
> I really dont see the plethora of sec-id# that are currently generated
> being really useful since they change on each export if new stuff is
> entered. This make existing CSS redundant unfortunately.


Forgot to say: the ID's are, what the links in the TOC jump to. Also,
they're needed for org-info.js to resolve internal links to sections in
general.

Best,

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Http:  www.emma-stil.de


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Sebastian Rose
Sebastian Rose  writes:
>> So one that wraps everything in body.  OK, let's call it "content".
>>
>> And then one that does contains the sections and footnotes, but
>> not the title, preamble, and postamble?  Am I understanding this
>> correctly?
>
>
> Just the outer one then. As long as noone uses an container we shouldn't
> add it.
>
> Even the inner one with all the sections is merely a matter of taste.

Sorry for replying to my own mail.

By `taste' I mean the possible layouts when section _and_ footnotes & Co
are wrapped into one container, versus just sections in one container
but not footnotes & Co

I really should make a training in reading and writing mails :)


Regards,

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Http:  www.emma-stil.de


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Problem with archiving

2009-03-02 Thread Ed Hirgelt
Using the latest from git:  when I try to archive a subtree with C-c  
$, I get


org-archive-subtree: Wrong type argument: number-or-marker-p, nil

Archive is going to the default location, in my case Tasks.org_archive  
in the

same directory.  This also failed with a newly created file.

Thanks,
Ed




___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Problem with archiving

2009-03-02 Thread Nick Dokos
Ed Hirgelt  wrote:

> Using the latest from git:  when I try to archive a subtree with C-c  
> $, I get
> 
> org-archive-subtree: Wrong type argument: number-or-marker-p, nil
> 
> Archive is going to the default location, in my case Tasks.org_archive  
> in the
> same directory.  This also failed with a newly created file.
> 

I can see this too:

Org-mode version 6.23trans
GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-07-01 on 
alphaville.zko.hp.com



___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] Re: DocBook exporter for Org-mode

2009-03-02 Thread Baoqiu Cui
Baoqiu Cui writes:
 > Hello Dominik,

Sorry, I meant "Prof. Dominik".  The email address misled me. :-)

Baoqiu

 > use it two weeks ago.  I've been using (X)Emacs since 1995, and had
 > tried to use Muse about 2-3 years ago for note-taking and simple
 > publishing (i.e. generating LaTeX or DocBook documents from Muse).
 > However, I remember I ran into some serious limitations (like list
 > handling, etc.) in Muse and finally gave up on it.  I went back to
 > writing documentation directly in either LaTeX or DocBook (I use nXML
 > mode for DocBook editing).
 > 
 > Org-mode impressed me with its nice table editing functionality,
 > flexible/powerful list support and headline (or section/subsection)
 > manipulations, and *many* other features.  I really appreciate your work
 > on this valuable package, and foresee that I will be doing many more
 > things in Org-mode.
 > 
 > The only thing that is missing (at least to me) in current Org-mode is
 > the exporter for DocBook format.  DocBook is becoming more and more
 > popular, so a DocBook exporter in Org-mode could make more people move
 > to Org-mode.  Also, since there are a lot open-source or commercial
 > tools to convert DocBook format to almost any other formats (PDF,
 > PostScript, HTML, XHTML, Text, RTF, etc.), DocBook exporter could be the
 > main exporter that Org-mode needs to support.
 > 
 > During the last week (mainly during the last weekend), I wrote some code
 > to export Org files to DocBook V5.0 format, and everything looks very
 > promising (I have to admit that a lot of work still needs to be done to
 > make the code complete and stable) .  I am wondering how I can
 > contribute the code to Org-mode.
 > 
 > I am attaching a PDF file generated from a DocBook XML file that was
 > exported by my org-export-docbook.el, and would like to get your early
 > feedback/comments.
 > 
 > 
 > Regards,
 > Baoqiu


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Richard Riley
Sebastian Rose  writes:

> Richard Riley  writes:
>> I really dont see the plethora of sec-id# that are currently generated
>> being really useful since they change on each export if new stuff is
>> entered. This make existing CSS redundant unfortunately.
>
> The IDs in the section headings are not meant for CSS styling. That's
> what the classes are for.
>
>
> Regards,

IDs are frequently used for styling as well as classes.

-- 
 important and urgent problems of the technology of today are no longer the 
satisfactions of the primary needs or of archetypal wishes, but the reparation 
of the evils and damages by the technology of yesterday.  ~Dennis Gabor, 
Innovations:  Scientific, Technological and Social, 1970


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Switching between many contexts

2009-03-02 Thread Matthew Lundin
Hi Daniel,

Daniel Clemente  writes:

>   Hi. I have this scenario: I track several projects in a single file, each 
> in its own level-1 section, but each week I'm working only on one project.
>   In my agenda (C-a a) I'm currently seeing scheduled tasks from all 
> projects, and I would like to exclude all projects but one.
>   I recently added a CATEGORY property to each section.

There are a couple of FAQs on this subject:

http://orgmode.org/worg/org-faq.php#limit-agenda-with-tag-filtering

http://orgmode.org/worg/org-faq.php#limit-agenda-with-category-match

I would use tags in such a scenario. Simply give each project a unique
tag and then use secondary filtering to limit the agenda to that tag (as
Bernt explains in the other posts on this thread).

Best,
Matt


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Sebastian Rose
Richard Riley  writes:
> Sebastian Rose  writes:
>
>> Richard Riley  writes:
>>> I really dont see the plethora of sec-id# that are currently generated
>>> being really useful since they change on each export if new stuff is
>>> entered. This make existing CSS redundant unfortunately.
>>
>> The IDs in the section headings are not meant for CSS styling. That's
>> what the classes are for.
>>
>>
>> Regards,
>
> IDs are frequently used for styling as well as classes.


Well, in this case, since we never know the ID of a section in
advance... 


-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Http:  www.emma-stil.de


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] export and containers

2009-03-02 Thread Richard Riley
Sebastian Rose  writes:

> Richard Riley  writes:
>> Sebastian Rose  writes:
>>
>>> Richard Riley  writes:
 I really dont see the plethora of sec-id# that are currently generated
 being really useful since they change on each export if new stuff is
 entered. This make existing CSS redundant unfortunately.
>>>
>>> The IDs in the section headings are not meant for CSS styling. That's
>>> what the classes are for.
>>>
>>>
>>> Regards,
>>
>> IDs are frequently used for styling as well as classes.
>
>
> Well, in this case, since we never know the ID of a section in
> advance... 

Or haven't known in the past. See other post. We probably need to be
able to control the class and/or ID of individual sections at the higher
level.


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[Orgmode] done-ing a repeating scheduled task now inserts closed timestamp?

2009-03-02 Thread Samuel Wales
Nobody else has commented on this, so perhaps I am doing something wrong.

My recollection is that [setting the todo state of a task with a
repeating scheduled task to done] did not used to insert a closed
timestamp, but now it seems to -- or at least it fails to remove the
timestamp.  Is this intentional?

I use the closed timestamp to indicate that a task can be archived,
but perhaps I should not rely on that?


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Problem with archiving

2009-03-02 Thread Nick Dokos
Ed Hirgelt  wrote:

> Using the latest from git:  when I try to archive a subtree with C-c 
> $, I get
> 
> org-archive-subtree: Wrong type argument: number-or-marker-p, nil
> 
> Archive is going to the default location, in my case Tasks.org_archive
> in the
> same directory.  This also failed with a newly created file.
> 

Here's a little more information on what goes wrong:

 foo.org -

* foo
** bar
** baz
--

C-c $ (on the * foo line) then gives:

Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
  org-get-valid-level(0 nil)
  org-archive-subtree(nil)
  call-interactively(org-archive-subtree nil nil)


the suspect line in org-archive.el being:

  ...
  ;; Paste
  (org-paste-subtree (org-get-valid-level level (and heading 1)))
  ...

heading was evaluated to "" and then set to nil, so (and heading 1) evaluates
to nil (it probably should evaluate to 0?), which is used in org-get-valid-level
as a number to be added to the level.

Should (and heading 1) become (if heading 1 0)?


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] outline-agenda sorting consistency

2009-03-02 Thread Samuel Wales
Hi Carsten,

On Thu, Feb 19, 2009 at 12:22, Carsten Dominik  wrote:
>> 1) priority faces are settable in the agenda.  perhaps
>>   they could be so in the outline also.
>
> This seems more confusing than useful to me.  In the agenda,
> all the tasks are together, so it does make some sense to
> change fonts.  In the outline, I would find it confusing.
> Are there any other opinions on this?

I'll try to provide more detail for at least my case.

I would not set the face for the whole headline, just the
priority tag itself.  I actually find the agenda faces,
which often set the entire headline, to be confusing.[1]

I would not propose to change the default.

For me [#C] and [#A] look alike and it is hard to
distinguish them based on the single letter.  I basically
stopped using C because I kept (mis)perceiving it as
important.  (I don't use B because it is the same as blank.)

What I would do is set C to show in something like (but not
the same as) the done todo kw face, and A to show in
something like the todo face.  This tells me to pay
attention less and more, respectively.  Others would
semioticize (so to speak) differently.

>> 2) sorting strategy is settable in the agenda.  perhaps it
>>   could be settable in the outline also.  they could
>>   share code.
>
> To be honest, I never sort the outline, except in rare cases.
> I would be interested how people use this to get a better case
> for changing this.

I would use it to keep high urgency and -priority tasks at
the top and done tasks at the bottom.

Also, I sometimes have a large list of disorganized tasks.
The tasks need todo state specification, tagging, priority
setting, refiling, turning into a plain list, etc.; and
sorting seems the best way to focus the organizing.  I can
only do a little at a time, and can't predict when I can do
it, so having it sorted allows me to immediately see gaps.
Like "this is too urgent to be among the non-urgent tasks".
Then I can return to it later without having to
refamiliarize myself with the whole list.

I can more easily isolate the high priority and high urgency
stuff that isn't done, then organize only that.  After
dealing with metadata, I can make the hierarchy deeper by
ontology.


Having it work like org-agenda-sorting-strategy would allow
the same sorting in both places.

Here is how I might do it, were the facility to exist:

  - done-ish and unimportant stuff at the bottom, important
stuff at the top, and uncategorized nodes (i.e. blank
todo state, no priority, no urgency) in the middle.
  - alphabetical order for nodes with the same weight
  - to calculate the weight of a node:
1) priority a is worth +1000
2) urgent tag gets +1000
3) now tag gets +500
4) todo-ish states (todo, next) get +100
5) /blank todo state/ gets 0
6) zombie states (wait etc.) get -100
7) someday tag gets -500
8) priority c gets -1000
9) done-ish states (done, moot) get -3000
  - example: an urgent todo would have a weight of 1100.
when it is marked done, it would have a weight of -2000.

This is especially useful for long confusing lists.

> One of the basic principles in Org is that in the notes files,
> tasks are in context.  In the agenda, things are re-arranged
> and sorted.  That is why there is a complex sorting strategy
> in the agenda, but not in the outline.

The agenda is wonderful for other stuff, but for me it is
not an editing mode per se.  I have never been able to use
the agenda for full control over the org file, as some
people are able to do.  For me (at least on my computer) it
is slow.  Arbitrary editing is not possible.  The keys that
work are often different from the ones I use in the outline.
If I define a key in the outline, I have to figure out how
to define it in the agenda (haven't yet).  I find
manipulating windows to be cumbersome, especially since for
accessibility reasons I have no option but to use very large
fonts that make split windows show very few lines (I
typically never split windows).  I usually can't see all the
tags in the agenda because there are not enough columns.  I
can't scroll the other window in follow mode.  Extra
keystrokes are required to organize things.  I can't easily
create an arbitrary outline view of all tasks under a node
with it.  I can't rearrange and sort as I would in the
outline.

So for me, while the agenda is indispensable, it is only for
showing an agenda view and occasionally jumping to a place.
Not for arbitrary sorting and organizing.

Just a different perspective / user experience.  I hope it's
useful in some way at least.


[1] Especially since some elements get recolored
(refaced) from the way they are in the outline.  e.g. done
todo kw showing up as todo face or tags being recolored.
Might be bugs or might be overloading (because there is
deadline and scheduled information being added to the
information that is already in the headline).  A possible
solution is to reface just the category, or to have a single

Re: [Orgmode] Problem with archiving

2009-03-02 Thread Carsten Dominik

Fixed, thanks.

Nick, also thanks for so quickly confirming this bug and for
the correct analysis.

- Carsten

On Mar 2, 2009, at 8:11 PM, Ed Hirgelt wrote:

Using the latest from git:  when I try to archive a subtree with C-c  
$, I get


org-archive-subtree: Wrong type argument: number-or-marker-p, nil

Archive is going to the default location, in my case  
Tasks.org_archive in the

same directory.  This also failed with a newly created file.

Thanks,
Ed




___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode




___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Fwd: [Orgmode] ascii export of url part of links possible?

2009-03-02 Thread Carsten Dominik



Begin forwarded message:


From: Carsten Dominik 
Date: March 3, 2009 6:54:14 AM GMT+01:00
To: Samuel Wales 
Cc: Carsten Dominik 
Subject: Re: [Orgmode] ascii export of url part of links possible?

I think we need more testers here, could someone please come aboard?
I cannot reproduce the bug Samuel is describing.

- Carsten

On Mar 2, 2009, at 7:08 PM, Samuel Wales wrote:


Now using 6.23trans.

Whether it is fn or footnotes, I now get this output.


this is a test[1].  it is also a test[2].  and it
has a link [google link one].  and another [3] and another
[yahoo link two].[4]

footnotes
[fn:39] four
[1] one

[2] two

[3] three

[4] [fn:39]


[google link one]: googlelink.com
[yahoo link two]: yahoolink.com


On Mon, Mar 2, 2009 at 07:00, Carsten Dominik  
 wrote:

Still, not a problem that I can reproduce.

- Carsten

On Mar 2, 2009, at 8:42 AM, Samuel Wales wrote:


Just this:

(setf org-footnote-auto-label 'confirm)
(setf org-footnote-section nil)

On Sun, Mar 1, 2009 at 22:35, Carsten Dominik >

wrote:


I cannot reproduce this.  What is your footnote-related setup?

- Carsten

On Feb 27, 2009, at 10:27 PM, Samuel Wales wrote:


Hi Carsten,

Thanks.

I tried to break it and succeeded.

 1.  the url for google is replaced with the url for
   yahoo.
 2.  the links are on one line.
 3.  if you replace "footnotes" with "fn" you will get a
   footnote formatting error.

IMO if poss it is best to continue to collect all links into a  
links

section and not use footnotes.

* test export
this is a test[fn:36].  it is also a test[fn:37].  and it
has a link [[googlelink.com][google link one]].  and another  
[fn:38] and

another
[[yahoolink.com][yahoo link two]].[fn:39]

footnotes

[fn:36] one

[fn:37] two

[fn:38] three

[fn:39] four

Output:

this is a test[1].  it is also a test[2].  and it
has a link [google link one].  and another [3] and another
[yahoo link two].[4]

footnotes

[1] one

[2] two

[3] three

[4] four


[yahoo link two]: yahoolink.com[google link one]: yahoolink.com

--
Myalgic encephalomyelitis denialism is causing death (decades  
early;
Jason et al. 2006) and severe suffering, pain, and disability  
(worse

than nearly all other serious diseases studied; Schweitzer et al.
1995) and grossly corrupting science.  Anybody can get the  
disease at
any time.  http://www.meactionuk.org.uk/ 
What_Is_ME_What_Is_CFS.htm







--
Myalgic encephalomyelitis denialism is causing death (decades  
early;
Jason et al. 2006) and severe suffering, pain, and disability  
(worse

than nearly all other serious diseases studied; Schweitzer et al.
1995) and grossly corrupting science.  The denialism is worse  
than it

ever was with even AIDS or MS.
http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm







--
Myalgic encephalomyelitis denialism is causing death (decades early;
Jason et al. 2006) and severe suffering, pain, and disability (worse
than nearly all other serious diseases studied; Schweitzer et al.
1995) and grossly corrupting science.  The denialism is worse than it
ever was with even AIDS or MS.
http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm




___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] org-exp-bibtex.el - add support to citing bibtex in both html and latex exports

2009-03-02 Thread Taru Karttunen
On 02.03 10:40, William Henney wrote:
> > Selecting only some entries to display would be possible,
> > but is it really necessary? In my use cases I just tend
> > to have a per-article bib-file that contains the entries
> > I wish to use. Making a rich enough API to sort, reformat
> > and select a portion of a BibTeX file seems quite overblown
> > for org.
> 
> Personally, I use a single .bib file for everything, which is
> currently running at 12269 entries, so something like Carsten's
> suggestion would be necessary before org-exp-bibtex.el became useful
> to me :)
> 
> Bibtex2html already comes with a separate tool "bib2bib" which seems
> to already do exactly what is needed. See
> http://www.lri.fr/~filliatr/bibtex2html/doc/#htoc12

Yes, it contains bib2bib and even the main bibtex2html contains
functionality for this.

Now how do we want to do this with org-mode?
1) The user is responsible for creating a bib-file using
whatever tools she prefers (e.g. bib2bib).
2) Add an option to just select the entries that are used
in the org-file. Nothing fancy.
3) Add a generic API to select+sort+format the entries.

Both 1 and 2 are easy to do. I can create a patch that 
adds support for this later this week. Are there any
other features that you would need?

- Taru Karttunen


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode