Christer Enfors <[email protected]> writes: > Becoming an org contributor liaison (thanks for that opportunity!) has > really motivated me to try to learn enough Elisp so that I can > contribute actual code as well. And I'm really excited about that > notion, but I need to learn more before I can do anything concrete about > it.
:) One way to learn Elisp is fixing some easier bugs. That way, you will get familiar with the existing code, the ways it can break, and the ways to fix things. I have also been thinking to make a spin-off for OrgMeetup dedicated to helping people get started with fixing bugs or implementing features for Org. > But, incidentally, I wrote the following in one of my Org files earlier > today: > > ***** Better display of long appointments in agenda time grid > > - Sometimes you have appointments which span several "slots" in > 'org-agenda-time-grid', and currently the lines in the grid after the > first one look empty, even though they are "occupied" by an > appointment that's only listed on its first time-matching line on the > grid. For example: > > - 08:00...... ---------------- > 09:00-11:00 Sync meeting > 10:00...... ---------------- > 11:00...... ---------------- > 12:00...... ---------------- > > - Even though the meeting is listed as being from 09:00 to 11:00 on > its line, the 10:00 slot still looks empty even though the meeting > is still ongoing then. > > - This could be displayed in several better ways: > > - Skipping the deceptively empty-looking slot at 10:00: > > - 08:00...... ---------------- > 09:00-11:00 Sync meeting > 11:00...... ---------------- > 12:00...... ---------------- > > - Displaying the meeting on all relevant lines: > > - 08:00...... ---------------- > 09:00-11:00 Sync meeting > 10:00...... | Sync meeting (cont) > 11:00...... ---------------- > 12:00...... ---------------- > > - Displaying only a pipe on subsequent lines to "occupy" the space: > > - 08:00...... ---------------- > 09:00-11:00 Sync meeting > 10:00...... | > 11:00...... ---------------- > 12:00...... ---------------- This is a fine idea, although probably not the best to get started. org-agenda is notoriously fragile historical code where even I struggle to navigate at times. Of course, with enough dedication, you can still add some features there, but that will be a pain. Also, have you seen https://github.com/ichernyshovvv/org-timebloc? If you want to implement some new feature, we have a list of possible features (of varying complexity) in https://tracker.orgmode.org/?types=request If you want, I can look through that list and my records and suggest something easy to get started. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
