From: Kevin Foley <kfoley15@gmail.com>
To: gcr@wisdomandwonder.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel Edit Code Whole Session Context
Date: Sun, 24 Jun 2018 15:46:13 -0400 [thread overview]
Message-ID: <CAF96XX1Qn17HZiH8FcM4Y_06EtozSBUFY0t8ac+3rwL15PD9gA@mail.gmail.com> (raw)
In-Reply-To: <CAAjq1mf9pmytku2fAc7pdGEifVrEqQBNE1hOd3w=p8XDCuNWfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Hi Grant,
> I hear you and think I understand what you say. I also know it can be
> irritating when
> somebody answers a slightly different question question you asked. If
> you humor me,
> I'm about to do that.
No problem, I appreciate all discussion on the matter.
> I don't know how to do what you ask. However, I have something to do
> that I would be
> pretty happy.
> 1. Set the default headers args to noweb :tangle
> 2. Develop blocks normally, without Company.
> 3. When I am ready to work on the whole codebase with company, tangle
> to a file.
> 4. Go to that file. Leverage Company and make changes. When you are
> done detangle.
> 5. Iterate
I'm thinking of trying to implement something similar. My solution would
be to place all code from blocks of the same session into the edit buffer
and then narrow to only the section from the current code block. Then all
features should work seamlessly. I'm not quite sure the best approach to
do this but I'm going to start poking around in the source code to see if
it's feasible.
If anyone has a solution that's already available or any feedback on my
proposed approach I'd greatly appreciate it.
--
Thanks,
Kevin Foley
[-- Attachment #2: Type: text/html, Size: 2929 bytes --]
prev parent reply other threads:[~2018-06-24 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 14:50 Babel Edit Code Whole Session Context Kevin Foley
2018-06-24 16:10 ` Grant Rettke
2018-06-24 19:46 ` Kevin Foley [this message]
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=CAF96XX1Qn17HZiH8FcM4Y_06EtozSBUFY0t8ac+3rwL15PD9gA@mail.gmail.com \
--to=kfoley15@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gcr@wisdomandwonder.com \
/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).