Project Description

I'd like to have NeoMutt show an index of emails at the same time as the body of the selected email, horizontally next to each other.

Goal for this Hackweek

I will to work on option for NeoMutt which allow index and pager pane to be split horizontally (side-by-side).

It looks like I am not the only one which will like this functionality [1, 2].

Email client repository could be found here [3].

[1] Can mutt show the index and body of emails in a horizontal split?

[2] Show index and body of emails in a horizontal split (side-by-side)

[3] Source Code

Resources

Looking for hackers with the skills:

c

This project is part of:

Hack Week 20

Activity

  • over 4 years ago: iivanov started this project.
  • over 4 years ago: mkubecek liked this project.
  • over 4 years ago: mbrugger liked this project.
  • over 4 years ago: iivanov added keyword "c" to this project.
  • over 4 years ago: iivanov originated this project.

  • Comments

    • iivanov
      over 4 years ago by iivanov | Reply

      Code changes which adds side-by-side index and page layout could be found here.

      New behaviour is controlled by pager_columns option.

      Non-zero value defines how many columns to be used for pager (email content displaying window).

      pager_columns overwrites pager_index_lines option. This means that the index (window which display email subject, date...) will occupy all screen rows.

      Result is not what I have expected add-emoji . Screen should be biggish to be able to display whole Subject, Date, Author information.

      Screenshot

    • iivanov
      over 4 years ago by iivanov | Reply

      Open Build service project for this could be found here

    • iivanov
      over 4 years ago by iivanov | Reply

      I have send pull request with the changes upstream.

    Similar Projects

    pudc - A PID 1 process that barks to the internet by mssola

    Description

    As a fun exercise in order to dig deeper into the Linux kernel, its interfaces, the RISC-V architecture, and all the dragons in between; I'm building a blog site cooked like this:

    • The backend is written in a mixture of C and RISC-V assembly.
    • The backend is actually PID1 (for real, not within a container).
    • We poll and parse incoming HTTP requests ourselves.
    • The frontend is a mere HTML page with htmx.

    The project is meant to be Linux-specific, so I'm going to use io_uring, pidfs, namespaces, and Linux-specific features in order to drive all of this.

    I'm open for suggestions and so on, but this is meant to be a solo project, as this is more of a learning exercise for me than anything else.

    Goals

    • Have a better understanding of different Linux features from user space down to the kernel internals.
    • Most importantly: have fun.

    Resources