emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lele Gaifax <lele@metapensiero.it>
To: emacs-orgmode@gnu.org
Subject: Re: latex-export + columnview: misinterpretation of section prefixes as emphasis
Date: Fri, 24 Jun 2016 14:08:39 +0200	[thread overview]
Message-ID: <871t3mvlfc.fsf@metapensiero.it> (raw)
In-Reply-To: 87bn2r7wps.fsf@saiph.selenimh

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Lele Gaifax <lele@metapensiero.it> writes:
>
>> One minor issue: previously I used a custom setting for the variable
>> `org-time-clocksum-format`, to print something like "2gg 03:10" instead of "2d
>> 03:10". With the version currently distributed with Emacs 25.1 it was used for
>> both the "effort" and "clocksum" columns, now only on the latter (matching
>> name and documentation). Is there an equivalent setting for the "effort"
>> sum, to get a table with the two columns sharing the same style?
>
> I don't think so, but I may be wrong. Anyway, you can define your own
> summary function (and formatter) in Org colums. See
> `org-columns-summary-types' for details.

This is a simple file, made with the version of org-mode that comes from
current Emacs 25 branch:

    # -*- coding: utf-8 -*-
    #+TITLE: Test with Emacs 25.0.95 org-mode
    #+COLUMNS: %40ITEM(Item) %13Effort(Effort){:} %CLOCKSUM(Work)

    * This is a test
      CLOCK: [2016-06-21 mar 13:40]--[2016-06-24 ven 13:43] => 72:03

    #+BEGIN: columnview :hlines 1 :id global
    | Item             |   Effort | Work     |
    |------------------+----------+----------|
    | * This is a test | 1gg 6:00 | 3gg 0:03 |
    | ** Task A        |    10:00 |          |
    | ** Task B        |    10:00 |          |
    | ** Task C        |    10:00 |          |
    #+END:

    ** Task A
       :PROPERTIES:
       :Effort:   10:00
       :END:

    ** Task B
       :PROPERTIES:
       :Effort:   10:00
       :END:

    ** Task C
       :PROPERTIES:
       :Effort:   10:00
       :END:

    # Local Variables:
    # org-time-clocksum-format: (:days "%dgg " :hours "%d" :require-hours t :minutes ":%02d" :require-minutes t)
    # End:

This is the equivalent, made with current master development org-mode:

    # -*- coding: utf-8 -*-
    #+TITLE: Test with current master revision of org-mode
    #+COLUMNS: %40ITEM(Item) %13Effort(Effort){:} %CLOCKSUM(Work)

    * This is a test
      :LOGBOOK:
      CLOCK: [2016-06-21 mar 13:40]--[2016-06-24 ven 13:43] => 72:03
      :END:

    #+BEGIN: columnview :hlines 1 :id global
    | Item           | Effort | Work     |
    |----------------+--------+----------|
    | This is a test |  30:00 | 3gg 0:03 |
    | Task A         |  10:00 |          |
    | Task B         |  10:00 |          |
    | Task C         |  10:00 |          |
    #+END:

    ** Task A
       :PROPERTIES:
       :Effort:   10:00
       :END:

    ** Task B
       :PROPERTIES:
       :Effort:   10:00
       :END:

    ** Task C
       :PROPERTIES:
       :Effort:   10:00
       :END:

    # Local Variables:
    # org-time-clocksum-format: (:days "%dgg " :hours "%d" :require-hours t :minutes ":%02d" :require-minutes t)
    # End:

Can you reproduce the case?

>> BTW, in lisp/org-colview.el there is what seems a typo in the name of the
>> function `org-columns-hscoll-title`: since accordingly with "git grep" it is
>> referenced in two places and only in that source, is the following
>> acceptable?
>
> Sure. Could you provide a proper commit message and send the patch using
> "git format-patch" command? See
> <http://orgmode.org/worg/org-contribute.html#patches> for details.

Sure, I will do that ASAP!

Thank you,
ciao, lele.
-- 
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it  |                 -- Fortunato Depero, 1929.

  reply	other threads:[~2016-06-24 12:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31  3:38 latex-export + columnview: misinterpretation of section prefixes as emphasis Juan Pechiar
     [not found] ` <D96E521D-17DE-4725-AD9A-363522C9B1E9@tsdye.com>
     [not found]   ` <20100531130409.GE27574@soloJazz.com>
2010-05-31 16:57     ` Thomas S. Dye
2010-06-01  7:32 ` Carsten Dominik
2010-06-01 10:51   ` Tim Burt
2010-06-01 13:34     ` Carsten Dominik
2010-06-01 14:52       ` tcburt
2016-06-22 18:45 ` Lele Gaifax
2016-06-22 19:56   ` Nicolas Goaziou
2016-06-22 20:16     ` Lele Gaifax
2016-06-22 20:46       ` Nicolas Goaziou
2016-06-23  6:36         ` Lele Gaifax
2016-06-24  9:38           ` Nicolas Goaziou
2016-06-24 12:08             ` Lele Gaifax [this message]
2016-06-24 12:26               ` [PATCH] org-colview.el: Fix typo in function name Lele Gaifax
2016-06-24 12:49                 ` Nicolas Goaziou
2016-06-24 13:06                   ` Lele Gaifax
2016-06-24 14:01                     ` Nicolas Goaziou
2016-06-24 12:47               ` latex-export + columnview: misinterpretation of section prefixes as emphasis Nicolas Goaziou
2016-06-24 13:03                 ` Lele Gaifax

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871t3mvlfc.fsf@metapensiero.it \
    --to=lele@metapensiero.it \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).