pimutils / pimutils/khal

Uneven tab application per calendar in `khal calendar`

Open
#906 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

pri:Low type: bug
Dominant language
Python
Stars
3.1k
Forks
233
Avg merge
1h 44m
Merged PRs (30d)
1

Description

I am using the {tab} character in my agenda_event_format: "{calendar-color}{cancelled}{start-end-time-style}{tab}{title}{repeat-symbol} {reset}{calendar}{reset}", and here is my output.

[cassie@houndoom ~]$ khal calendar -a Calendar -a Classes
    Su Mo Tu We Th Fr Sa     [2020-02-05] Today
Feb 26 27 28 29 30 31  1     |->  Vivian Visits Calendar
     2  3  4  5  6  7  8     10:00-10:50    PHL-1100-102 LOGIC I (R) Classes
     9 10 11 12 13 14 15     11:00-11:50    RC-2001-120 INTR WRITING ACROSS CURRICULUM (R)
    16 17 18 19 20 21 22     Classes
    23 24 25 26 27 28 29     14:00-14:50    AST-1002-102 INTRO AST II/STAR GALAX (R) Classes
Mar  1  2  3  4  5  6  7     15:30-16:45    PHL-2000-104 PHILOSOPHY, SOCIETY & ETHICS (R)
     8  9 10 11 12 13 14     Classes
    15 16 17 18 19 20 21     17:00-18:00  Pay Ticket Deadline Calendar
    22 23 24 25 26 27 28     22:00-23:50    AST-1002-206 Laboratory (R) Classes
Apr 29 30 31  1  2  3  4     [2020-02-06] Tomorrow
     5  6  7  8  9 10 11     ->|  Vivian Visits Calendar
    12 13 14 15 16 17 18     09:30-10:45    PHL-1501-101 MIND, KNOWLEDGE & REALITY (R) Classes
    19 20 21 22 23 24 25     11:00-14:00  Rivers Street (noodles) (R) Calendar
May 26 27 28 29 30  1  2

This is easier to read in a screenshot, posted here.

While the duration formats are the same length on different events, it seems that depending on the calendar there are different tab lengths applied to each event.

Despite the intended function of the tab control code, I would love to be able to format the list in some sort of column-based output, so that I could have a column each for time, summary, and calendar name. I await the discussion in this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the shown khal calendar -a Calendar -a Classes output with the supplied agenda_event_format and {tab} control code. Compare tab expansion across events and calendars, then define and verify consistent columns for time, summary, and calendar name; the issue thread contains the discussion to review before deciding what “done” means.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.