Re: [O] Please test the new Makefile
Hi. Achim, Thank you for your kind explanations. I learned a lot from you :) > I opted for this behaviour to align more closely to GNU convention and to > avoid any surprising behaviour, but it is easy to make the default target > "all" instead of "help". I think many Org users are familiar to the previous installation procedure by "make" not "make all", and some users wrote it in their blog, Org manual [*1] too. Don't you think this change has a wide impact for them? But it's just a concern to me :) [*1] http://orgmode.org/manual/Installation.html
Re: [O] Inconsisent typesetting of commands in the manual
Dear Elias and all,
> In section 2.7 on p. 14--15 in the full manual for Org-mode the key commands
> is typeset in serif while all the other key commands in the manual is typeset
> in mono space fonts.
I think this is caused by "@table @asis" at L.1645 in doc/org.texi.
When I change it to "@table @kbd", it looks good.
But my suggestion is that the @table section is separated as follows:
*** 1664,1670
variable @code{org-M-RET-may-split-line}.}. If this command is executed
@emph{before item's body}, the new item is created @emph{before} the current
one.
! diff@kindex M-S-@key{RET}
@item M-S-@key{RET}
Insert a new item with a checkbox (@pxref{Checkboxes}).
@kindex S-@key{down}
--- 1664,1673
variable @code{org-M-RET-may-split-line}.}. If this command is executed
@emph{before item's body}, the new item is created @emph{before} the current
one.
! @end table
!
! @table @kbd
! @kindex M-S-@key{RET}
@item M-S-@key{RET}
Insert a new item with a checkbox (@pxref{Checkboxes}).
@kindex S-@key{down}
Best regards,
Takaaki Ishikawa
Re: [O] [DEV] Package org-find-timestamps on worg is now deprecated !
Am 20.12.2011 01:12, schrieb Bernt Hansen: Marc-Oliver Ihm writes: There is probably some overlap here, but I do not see a way to find the timstamps of CLOSED entries with the agenda. So the agenda does not show what you have accomplished, only what is still open. Another point are maybe inactive timestamps, which I use a lot to simply mark my notes with the current date. I do not know, if they readily show up in the agenda. Try this in the daily/weekly agenda view: C-u l to show clock logs, state changes, and closed time stamps [ to show inactive timestamps HTH, Bernt Hi Bernt, Hi list, Now I have checked the commands available in the agenda and you are right: The agenda already contains excellent functionality to do nearly all of the things, my package does. Therefore I deprecated it on Worg by adding this line: This module is now deprecated, because it mostly duplicates functionality already provided by the agenda; see the list of agenda commands and especially 'v l' for viewing logbook entries, 'v [' for showing inactive timestamps and 'j' to display the agenda for a specified date. Thanx again for pointing this out ! Before polishing my next package for publishing, I will first ask the mailing list for any pointers to prior art :-) with kind regards, Marc-Oliver Ihm
[O] Inconsisent typesetting of commands in the manual
Hello, In section 2.7 on p. 14--15 in the full manual for Org-mode the key commands is typeset in serif while all the other key commands in the manual is typeset in mono space fonts. Regards, Elias
Re: [O] Fw: [REQUEST] Microsecond timestamps
:) this is nice! - Carsten On 23.12.2011, at 22:23, Christian Moe wrote: > I'm forwarding this to the list as it was sent only to my mailbox by mistake. > -- Christian > > - > > > Dear Orgers, > > I would like to make a feature request for microsecond timestamps. > > Since I often find myself making a list and checking it twice, I think the > excellent Org mode would be a great way to schedule my deliveries. However, > the existing timestamp functionality just won't cut it for me. > > As my typical use case involves visiting over 2.5 billion homes in 48 hours, > I need to be able to schedule each TODO to microsecond accuracy. Please > consider developing this feature. > > Meanwhile, I'm happy to announce experimental Org support in our orders > department -- beta testers welcome! For the trial period we will give push > access to everyone on the Org mailing list who's been a good little girl or > boy all year. (So be good, for goodness sake!) Just do > > git clone git://north.pole/littlehelpersrepo.git > > Then simply add your items to wishlist.org, check that they're > cross-referenced to an up-to-date address in contacts.org, commit your > changes and push. > > Merry Christmas, everybody! Ho ho ho! > > Santa >
Re: [O] Please test the new Makefile
[sorry if you get this twice - GMane seems to have trouble sending lately] Am 22.12.2011 16:06, schrieb Takaaki ISHIKAWA: I think "make" and "make all" have the same effect usually. Often they do, but GNU says that a simple "make" should behave like "make help". I think this is appropriate for org mode since there is no INSTALL file that explains what to do and in most cases one would have to put some things in local.mk before running "make install". In the new Makefile of org-mode, however, "make" is used for displaying options of make command. Is this familiar to all? I opted for this behaviour to align more closely to GNU convention and to avoid any surprising behaviour, but it is easy to make the default target "all" instead of "help". For example, GNU Emacs doesn't require "make all", just "make". That's not exactly comparable since the Makefile for Emacs is the result of ./configure, so for Emacs make is just another tool used in a larger build system. -- Achim. (on the road :-)
Re: [O] Fw: [REQUEST] Microsecond timestamps
Christian Moe writes: > I'm forwarding this to the list as it was sent only to my mailbox by > mistake. -- Christian :) -- Bastien
Re: [O] LaTeX is typeset inconsequently
Bastien writes: > I just fixed this for the org.texi manual and will fix it for the > orgguide.texi later on. Done. -- Bastien
Re: [O] LaTeX is typeset inconsequently
Hi Elias, Elias Assarsson writes: > In both the full and the compact manual (Release 7.8.02) for Org-mode > "LaTeX" is typeset inconsequently. I just fixed this for the org.texi manual and will fix it for the orgguide.texi later on. Thanks for mentioning this! -- Bastien
