From: firstname.lastname@example.org To: TRS-80 <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Org Capture Menu cannot be fully viewed Date: Sun, 13 Dec 2020 00:30:09 +0100 [thread overview] Message-ID: <trinity-e878e596-42a8-4a84-9a3c-510e15b277e4-1607815809704@3c-app-mailcom-bs06> (raw) In-Reply-To: <email@example.com> > Sent: Sunday, December 13, 2020 at 12:13 AM > From: "TRS-80" <firstname.lastname@example.org> > To: email@example.com > Subject: Re: Org Capture Menu cannot be fully viewed > > On 2020-12-12 17:46, firstname.lastname@example.org wrote: > >> From: "TRS-80" <email@example.com> > > > > The problem also exists when making capture templates. The solution > > could be additional functionality coded in elisp that can then be used > > for handling longer template entries. As the problem is dependent on > > screen size, the problem is likely to occur, requiring the patch. It > > then becomes natural that the fix is introduced without the template > > developer having to call the fix explicitely. > > All true! > > > I assume it would involve some elisp and would be willing to word > > towards > > a solution. But it would be even better that the solution would be > > incorporated in the official version of emacs. > > What gets into Org / Emacs is up to maintainer(s?) and pending list > discussion. Which might take some time, but in many cases (I imagine > even including this one) is probably The Right Thing to do. That is understood. > If you can wait for that, it will end up improving Org and likely > helping a lot of people, including yourself (eventually). > > I guess some times I just prefer my own local "quick and dirty" solution > which can be "good enough" or a workaround pending a more proper > solution. Although, to be fair, the ability to maintain such solutions > (long term) is sort of dependent on knowing a bit of Elisp. So it's a > bit of a trade-off. > > I can send a long capture template. And any additional information > > people > > require. > > Well, it's up to you. If you want we can pursue either option, or both > (one potentially as a temporary workaround). Or we can wait for more > list replies and see what others think. As I said there may also be a > better way I am not aware of. If I'm being honest, I have plenty other > things to work on, too. ;) But since I open my big mouth now, I can't > very well leave you hanging, now can I? :D It also depends on how > complicated stuff we are talking... Very good of you. If you let me give a basic long template (perhaps "Investigation Site"). I can do both, get a fix, and work for an Emacs incorporation . > Actually, another option just occurred to me. I don't know where you > are sending results of the capture template, but if you are just > appending to file(s) perhaps you could break the one big template up > into some number of smaller ones? One problem with that is that new entries are appended in vertical (newline) and cannot put options in a table. > Cheers, > TRS-80 > >
next prev parent reply other threads:[~2020-12-12 23:32 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-12 18:02 pietru 2020-12-12 22:09 ` TRS-80 2020-12-12 22:46 ` pietru 2020-12-12 23:13 ` TRS-80 2020-12-12 23:30 ` pietru [this message] 2020-12-13 0:00 ` TRS-80 2020-12-13 0:10 ` pietru 2020-12-13 11:06 ` Jean Louis 2020-12-13 18:28 ` pietru 2020-12-13 20:37 ` Jean Louis 2020-12-13 20:52 ` TRS-80 2020-12-13 21:02 ` pietru 2020-12-13 21:48 ` Jean Louis 2020-12-13 22:08 ` pietru 2020-12-13 22:20 ` pietru 2020-12-13 22:00 ` TRS-80 2020-12-13 22:36 ` pietru 2020-12-13 20:32 ` TEC 2020-12-13 21:43 ` Jean Louis 2020-12-13 0:46 ` Tim Cross 2020-12-13 1:32 ` pietru 2020-12-13 2:08 ` pietru 2020-12-13 3:16 ` TRS-80 2020-12-13 3:49 ` pietru 2020-12-13 4:30 ` TRS-80 2020-12-13 9:58 ` pietru 2020-12-13 16:52 ` Jean Louis 2020-12-13 10:24 ` Jean Louis 2020-12-13 18:41 ` pietru 2020-12-13 20:48 ` TRS-80 2020-12-13 4:57 ` pietru 2020-12-13 9:24 ` Christopher Dimech 2020-12-13 23:08 ` TRS-80 2020-12-14 0:04 ` pietru 2020-12-13 9:44 ` Jean Louis 2020-12-13 18:46 ` Christopher Dimech 2020-12-16 18:46 ` No Wayman 2020-12-16 16:58 ` No Wayman 2020-12-13 15:12 ` Jean Louis 2020-12-13 18:08 ` pietru 2020-12-13 20:06 ` Tim Cross 2020-12-13 21:37 ` pietru 2020-12-13 21:57 ` Bastien 2020-12-13 22:31 ` pietru 2020-12-13 23:30 ` Jean Louis 2020-12-13 23:52 ` Bastien 2020-12-13 22:34 ` Jean Louis 2020-12-14 12:41 ` Marco Wahl 2020-12-14 13:00 ` pietru 2020-12-14 13:18 ` Marco Wahl 2020-12-14 20:02 ` Org Capture Menu cannot be fully viewed - Results of testing C-n, C-p, C-v pietru 2020-12-16 21:46 ` Marco Wahl 2020-12-16 23:25 ` pietru
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=trinity-e878e596-42a8-4a84-9a3c-510e15b277e4-1607815809704@3c-app-mailcom-bs06 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Org Capture Menu cannot be fully viewed' \ /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
Code repositories for project(s) associated with this 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).