-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have you considered overloading #+include:
?
#83
Comments
No. Because... What does "overloading" mean? 😅 |
Well, my thought is that |
oh yes. I see. I think you asked me this before on Reddit. I guess we can find out by having a branch and test out the idea. I'll see if I can do something tomorrow or in about two weeks time. I'm not going to sit in front of PC this evening and I will have a vacation for two weeks after tomorrow (probably with no laptop) ;) |
As an exploration, added a new branch explore/0.2.1-include. The idea is that when you export,
I'll stop here for now. I'll be checking GitHub on iPad but won't carry my laptop with me for my vacation; I'll come back in 2 weeks or so :) |
FWIW, that looks confusing to me, because the word "transclude" is nowhere to be found in it. :) I think that overloading |
So, I've ended up being unfortunately busy and juggling notifications (why life?), but seeing this mentioned on the Org ML recently jogged my memory about this. Regarding |
Soon after this conversation in June, I tried to change the code to support both I'm not settled either way, but I am leaning toward leaving
I think the same way, conceptually speaking. And this part of Ihor Radchenko's reply is going in the same direction:
Functionally, though, there are some differences. Notably, I don't seem to be able to support "noweb references" (I'm still unsure what this really is, but I know there is a limitation).
|
Personally, I see |
I think this could be nice, and so here's an issue for discussion 🙂
The text was updated successfully, but these errors were encountered: