should be now replaced with one of the two below:
git clone g...@code.orgmode.org:bzg/org-mode.git
git clone https://code.orgmode.org/bzg/org-mode.git
in the texi/Org manuals in maint/master.
--
Kaushal Modi
in the manuals be now replaced
with https://orgmode.org?
--
Kaushal Modi
mode.org/elpa.html.
--
Kaushal Modi
le HTML
page, so it takes a while to load. Do you know if there's a way to set it
up so that it shows a single page per node as orgmode.org does? Even if
not, this is wonderful :)
> --
Kaushal Modi
ng `ox-ascii' with stripped emphasis markers.
>
Exactly. That's why I suggested extending ox-ascii from this "raw" backend.
At this point, I'm not convinced we need this in Org proper.
>
That's understood. No problem. The snippet you suggested above serves the
purpose very well for now.
Thanks!
--
Kaushal Modi
t;raw"
backend spec, and we can discuss on the details.
--
Kaushal Modi
canonical approach) What would be the recommended
approach for an exporter backend to add new macros or override existing
macros (like "n" macro to wrap the string with HTML class as an example)?
Should it update org-macro-templates in org-export-before-processing-hook?
or something similar?
--
Kaushal Modi
On Wed, Dec 20, 2017 at 5:07 PM Nicolas Goaziou <m...@nicolasgoaziou.fr>
wrote:
> > If this looks good, I can commit this to maint.
>
> It looks good. Thank you.
>
Thanks. It's now committed to maint and merged to master.
--
Kaushal Modi
k of that as a
backend without even the minimal adornment that ox-ascii has... and
ox-ascii can be a derived backend from this one.
--
Kaushal Modi
part of `code'.
So the question: Is this the best way.. or is there a canonical way to
export an element without any markup char?
Full actual code[1].
[1]:
https://github.com/kaushalmodi/ox-hugo/blob/dffb7e970f33959a0b97fb8df267a54d01a98a2a/ox-hugo.el#L1769-L1802
--
Kaushal Modi
equired.
(when (plist-get info :with-special-strings)
(setq text (org-html-convert-special-strings text)))
=
After applying this patch, the same portion exported doesn't have
double-escaping before # and ![.
If this looks good, I can commit this to maint.
--
Kaushal Modi
succeeded and `git remote update' when the remote is the
> http version, succeeds as well.
I am seeing the same. The git: protocol fetch fails, but the http: protocol
fetch works.
Bastien, can you please look at this?
--
Kaushal Modi
On Mon, Dec 18, 2017 at 7:57 AM Ruy Exel <ruye...@gmail.com> wrote:
> Dear Kaushal,
>
> It took me a while to digest everything in your message, but I have
> finally managed to do my home-work and everything is now working
> perfectly! Thanks very much!
>
Great! You a
d to be sometimes different from the
current manual. This is not a 1:1 conversion.
Feedback welcome!
Regards,
--
Nicolas Goaziou0x80A93738
--
Kaushal Modi
on of the Org manual. Org can now eat its own
> dog food.
>
There are awesome news!
Would a template Org file be available that package authors can easily use
as a base to write their package manuals?
Many thanks! Will test it out next week.
--
Kaushal Modi
t; fatal: read error: Connection reset by peer
> > error: Could not fetch origin
>
> I can confirm this issue at least since 13th of December.
>
> Greetings
> Detlef
>
>
> >
> > If I recall correctly, this has happened before and the resolution was
> > that some admin needed to do something server-side.
> >
> > Thanks,
> > Josiah
> >
> >
>
>
>
>
> --
Kaushal Modi
With the above code, I just do C-x 8 to insert →.
Full code:
https://github.com/kaushalmodi/.emacs.d/blob/master/setup-files/setup-unicode.el
Hope that helps.
--
Kaushal Modi
ge/backend needs to be typed?
i.e. you insert a plain source block and point ends up where "|" is shown
below:
#+BEGIN_SRC |
#+END_SRC
--
Kaushal Modi
's up to the package author as to how much of hydra
features they want to pack into their package's hydras. hydra is not *just*
for showing available keys and/or *just* for chaining many single letter
commands. It's much more, in a good way.
--
Kaushal Modi
dling. With a bit
> of thought though, I think it could be integrated well.
>
I don't follow what the functional limitations are of what you said. How
does your concern affect a package author or the end user?
Adding @Oleh back to the thread.. hopefully he can weigh in.
--
Kaushal Modi
;" smerge-diff-base-lower)
("R" smerge-refine)
("E" smerge-ediff)
("C" smerge-combine-with-next)
("r" smerge-resolve)
("k" smerge-kill-current)
("q" nil "cancel" :color blue))
> > I quickly went though hydra.el.. isn't defhydra mainly what it is? What
> > would you suggest splitting out of that library?
>
> I don't know enough about it to have a clear opinion on that.
>
OK.
Thanks.
--
Kaushal Modi
t some X binding to get that popup interface.
I quickly went though hydra.el.. isn't defhydra mainly what it is? What
would you suggest splitting out of that library?
--
Kaushal Modi
both. I guess in the meantime, though,
> we're still going to have to use something else for the Org structure
> thing.
>
Correct. That's why I spawned off this "something for future" thread, and
did not talk about this in the original thread[1] :)
[1]: http://lists.gnu.org/r/emacs-orgmode/2017-12/msg00221.html
--
Kaushal Modi
Important advice?
>
Not trying to sound philosophical, but nothing is permanent. All the
package installations happen in the elpa dir.. so to start the Org
installation from scratch, you can rm -rf all the org installations from
the elpa/ dir and restart emacs following that "Important" instruction and
retry installing Org.
[1]: https://scripter.co/building-org-development-version/
--
Kaushal Modi
ble
and accessible:
[image: image.png]
There are so many places like this that can get a facelift from hydra.
Did I hear that Magit was breaking its popup interface out into a
> separate library? If so, that would also be a nice thing.
>
That would be great too. We are basically missing a configurable library to
bind temporary key maps, that can make the bindings present in a
discoverable way to the user. So far hydra.el fits the bill.
--
Kaushal Modi
On Tue, Dec 12, 2017 at 1:48 PM Eric S Fraga <esfli...@gmail.com> wrote:
> On Tuesday, 12 Dec 2017 at 14:02, Kaushal Modi wrote:
> > Copying this on both Emacs devel and Org mode list. Hopefully this
> > discussion is eligible for that.
> >
> > Problem statement
;> Nicolas, are there any public interfaces to make ox export like
> >> interfaces?
> >
> > No, there isn't. However, Org provides `org-mks'.
>
> Good point. It isn’t quite as nice as the export dispatcher. Let’s wait
> and see what Eric prefers.
>
--
Kaushal Modi
sion of the
manual from within Emacs.
PS: I figure this newbie message is not relevant to the folks at
> emacs-orgmode@gnu.org, so I'am not CCing it there anymore.
>
As I said in the beginning of the email, don't worry. We are all here to
learn and share.
> --
Kaushal Modi
o go
through the whole of
http://orgmode.org/cgit.cgi/org-mode.git/tree/etc/ORG-NEWS and make a note
of new features and few breaking changes since that version.
--
Kaushal Modi
ite source is on GitHub,
but it is published using Netlify (https://ox-hugo.scripter.co).
Another thing: GitHub Pages does not support https on custom domains..
Netlify does.
> thank you!
>
You are welcome.
And finally, let's move all non-Org discussion off the Org mailing list.
[1]: https://github.com/jwiegley/use-package/blob/master/.travis.yml
[2]:
https://github.com/jwiegley/use-package/blob/master/doc/setup-ox-hugo.el
[3]: https://github.com/blog/1509-personal-api-tokens
--
Kaushal Modi
website[3] the same way too, but using
Netlify (/which is the better than GitHub Pages or Gitlab CI IMO -- free
too/). See the footer of that site for the 1-file Org source.
[1]: https://github.com/jwiegley/use-package/blob/master/doc/Makefile
[2]: https://github.com/jwiegley/use-package/blob/master/use-package.org
[3]: https://ox-hugo.scripter.co/
--
Kaushal Modi
ultiple lines.
>
Ah, sorry, pilot error.
I had something like @@abc
def@@ in my actual test.. forgot the backend: string after @@.
Thanks!
--
Kaushal Modi
the rules in Org set to prevent auto-filling (like in Headings) be set
for Export Snippets too?
I am using the master branch, but I believe the same issue would be on
maint too.
Thanks.
--
Kaushal Modi
el 1
#+BEGIN_EXAMPLE
At level 1
#+END_EXAMPLE
- list level 2
#+BEGIN_EXAMPLE
At level 2
#+END_EXAMPLE
--
Kaushal Modi
i/ox-hugo/blob/832a5d7424013f60b77354ec28613440afac0269/ox-hugo.el#L2424-L2448
[3]: https://github.com/kaushalmodi/ox-hugo/blob/master/Makefile
--
Kaushal Modi
On Tue, Dec 5, 2017 at 11:44 AM Bastien Guerry <b...@gnu.org> wrote:
> I've fix something in the Worg publishing configuration, can you
> check again, maybe by making a test commit?
>
Thank you! It just made another commit and it got published instantly.
--
Kaushal Modi
I tried to find something equivalent in English
but couldn't :)
[1]: https://www.google.com/search?q=neki+aur+pooch+pooch
--
Kaushal Modi
On Sat, Dec 2, 2017 at 5:30 PM Nicolas Goaziou <m...@nicolasgoaziou.fr>
wrote:
> Hopefully fixed. Thank you.
>
Yes, I confirm the fix. Thank you!
--
Kaushal Modi
On Thu, Nov 16, 2017 at 9:23 AM Kaushal Modi <kaushal.m...@gmail.com> wrote:
>
> Shouldn't that commit update this page:
> http://orgmode.org/worg/org-blog-wiki.html ? But it hasn't been updated.
>
>>
That page hasn't yet updated.
And it looks like worg stopped up
rt-emacs-bug
> Is there a place to view submitted bugs and their resolution status?
>
Not that I know of. This seems to be an unofficial place to list those,
and doesn't look updated.
--
Kaushal Modi
. The same issue is
with all emphasis variants: italics, code, verbatim.
--
Kaushal Modi
s as soon as the first matching entry
is found?
- What's a better way to do the same?
Thanks.
--
Kaushal Modi
On Fri, Dec 1, 2017 at 9:00 AM Kaushal Modi <kaushal.m...@gmail.com> wrote:
> - How can I quit out of org-map-entries as soon as the first matching
> entry is found?
>
I think this is much better:
(let ((valid-found
(catch 'break
(org-map-entries
is risky, or at least should somehow be documented.
--
Kaushal Modi
s leave a blank line after #+RESULTS,
especially if they have one of these following the #+RESULTS: keyword?
(drawer example-block export-block fixed-width item plain-list src-block
table)
--
Kaushal Modi
On Tue, Nov 28, 2017 at 4:58 PM Kaushal Modi <kaushal.m...@gmail.com> wrote:
> I think that this behavior is on a safe side and good, but there needs to
> be a way for Org to figure out if the stuff following #+RESULTS is safe to
> delete..
>
> Can be probably
delete/overwrite the begin_results/end_results
blocks.
In the above example, Org cannot know if that example block is babel
generated or user-typed.
WDYT?
--
Kaushal Modi
On Mon, Nov 27, 2017 at 5:35 PM Nicolas Goaziou <m...@nicolasgoaziou.fr>
wrote:
> Ouch! Fixed. Thank you.
>
Thanks! I confirm the fix.
--
Kaushal Modi
-mode.git/commit/?id=1d8126385cf979cfaade0e6a82040884bd6af56b
--
Kaushal Modi
NAME style block
naming only when you want to call a Noweb block with an argument.
sorry for the noise
>
No worries.
> --
Kaushal Modi
ing (in exported files), there's also do:
#+INCLUDE: "./can-be-same-file.org::#CUSTOM_ID" :only-contents t
(See the "Include files" node in the Org manual for more.)
--
Kaushal Modi
On Mon, Nov 20, 2017 at 10:42 PM Eric Thomas <e...@ericthomas.net> wrote:
> * Here is an example of dot in action in orgmode
> <https://raw.githubusercontent.com/SeaDude/wtd-gitbook-pres/master/gitbook.org>
>
<>
<>
What an irony! :P
But a great example of dot-l
On Fri, Nov 17, 2017 at 6:30 PM Nicolas Goaziou <m...@nicolasgoaziou.fr>
wrote:
>
> You may want to test the following rules and report if it fits your use
> case.
>
That patch works great! Thanks!
--
Kaushal Modi
t/windows/
Try it out! :)
> --
Kaushal Modi
g tidily marked up.
>
I didn't follow all that you mentioned in the end. It's not clear what the
document restructuring was about after the initial problem statements.
Let's start with resolving the UNNUMBERED property non-inheritance.
> --
Kaushal Modi
as a :EXPORT_FILE_NAME: *property* in subtrees many
times, when doing subtree scoped exports, and it works great :) For subtree
exports, it's kind of mandatory to set that property if you want to export
different subtrees from the same Org file to different files.
> --
Kaushal Modi
me
line, and so resorted to tweaking org-emphasis-regexp-components. Overall
it works great, except for cases like these.
Again it's a font-locking bug, and thankfully doesn't impact the empasis
detection in exporters.
Would you please look into fixing this?
--
Kaushal Modi
-emph-re 'org-emphasis-regexp-components
org-emphasis-regexp-components)
=
[1]: https://i.imgur.com/6TmUoTS.png
--
Kaushal Modi
mit failed worg build?
Shouldn't that commit update this page:
http://orgmode.org/worg/org-blog-wiki.html ? But it hasn't been updated.
> --
Kaushal Modi
git repos, or I messed up my
worg commit (I reviewed the commit[1] again.. not sure what's wrong).
[1]:
http://orgmode.org/w/?p=worg.git;a=commitdiff;h=5c3afcbbd4d2c39e78f805008e2215470c908bbc
--
Kaushal Modi
ated with an entry, but you
> normally don’t want to see it. For this, Org mode has _drawers_. They
> can contain anything but a headline and another drawer.
*They can contain anything but a headline and another drawer.*
So I guess you have hit a limitation.
--
Kaushal Modi
On Wed, Nov 8, 2017, 7:27 AM Kaushal Modi <kaushal.m...@gmail.com> wrote:
> On Wed, Nov 8, 2017, 7:16 AM Bastien <b...@gnu.org> wrote:
>
>>
>> is there a simple mechanism in Emacs core to restore the same
>> functionnality?
>>
>
> +1
>
To clar
ans.
Given the lack of time, I just restored for works for me in my personal
config:
https://github.com/kaushalmodi/.emacs.d/commit/9aa3be89a2f8dce3f2aa57f98e0a2f38fdca4c6b
I just like the convenience of hitting "<s" and let the template insertion
logic do its thing.
Let me know what you think.
>
--
Kaushal Modi
On Mon, Nov 6, 2017 at 8:48 AM Nicolas Goaziou <m...@nicolasgoaziou.fr>
wrote:
> I documented the two changes above in ORG-NEWS.
>
Thanks!
--
Kaushal Modi
On Sun, Nov 5, 2017 at 9:24 AM Kaushal Modi <kaushal.m...@gmail.com> wrote:
> This is a breaking change though (org-try-structure-completion doesn't
> exist any more.. it breaks at least my config.. could be breaking more).
>
It could actually be a wider breakage as it change
ument.
> > * testing/lisp/test-org.el (test-org/insert-template): New test.
>
> Thank you. I applied your patch with the changes below.
>
I'll try this out soon. This is a breaking change though
(org-try-structure-completion doesn't exist any more.. it breaks at least
my config.. could be breaking more). Can you please also mention this
breakage in the ORG-NEWS?
--
Kaushal Modi
n't necessarily need the let form above, but that is in a form that
allows easily adding more languages in future.
--
Kaushal Modi
Hello all,
While trying to come up with a solution for this problem[1], I ended up
with a new problem :)
On Wed, Nov 1, 2017 at 11:51 AM Kaushal Modi <kaushal.m...@gmail.com> wrote:
> I still don't have a fully working solution (see below). Hopefully someone
> can help figure ou
On Wed, Nov 1, 2017 at 11:51 AM Kaushal Modi <kaushal.m...@gmail.com> wrote:
> I still don't have a fully working solution (see below). Hopefully someone
> can help figure out the reason for "Invalid read syntax: #" error.
>
OK, I found a workaround. Below solution
lt;ehdr(macro="SEC_FOO")>>
parameter A = 1;
#+END_SRC
** COMMENT Section 2: {{{SEC_BAR}}}
#+BEGIN_SRC verilog :noweb yes
<<ehdr(macro="SEC_BAR")>>
parameter A = 1;
#+END_SRC
=
--
Kaushal Modi
macrofy" in the
verilog code blocks?
Probably the solution is to use noweb references with arguments? See the
Org manual.
> --
Kaushal Modi
note reference to number 1.
The key is to not manually number the footnotes and let C-c C-x f (bound to
org-footnote-action) do its thing.
Hope that helps.
--
Kaushal Modi
halmodi/ox-hugo/ ).
On Tue, Oct 24, 2017 at 12:36 PM Marcin Borkowski <mb...@mbork.pl> wrote:
>
> FWIW, I did something similar some time ago:
> https://github.com/mbork/org-one-to-many
>
--
Kaushal Modi
t-command'."
(interactive)
(let ((is-region? (use-region-p)))
(if (or is-region?
(and (not is-region?)
(looking-back "^[[:blank:]]*")))
(hydra-org-template/body) ;Wrapper function for
`org-try-structure-completion'
(self-insert-command 1
--
Kaushal Modi
On Fri, Oct 20, 2017, 5:43 PM Kaushal Modi <kaushal.m...@gmail.com> wrote:
> On Fri, Oct 20, 2017 at 5:15 PM Eric Abrahamsen <e...@ericabrahamsen.net>
> wrote:
>
>> The template really only inserts the block type, not anything specific
>> like the source langua
an (GIF animation):
https://i.imgur.com/201TISW.gifv
I use hydra to provide those awesome hints.. but the same can be done
without hydras too.
As for what should be escaped and what shouldn't, I defer to Nicolas,
> let's see what he says.
>
--
Kaushal Modi
ot;))
replacing that whole (if ..) form.
--
Kaushal Modi
defined-blocks
deserves "SRC org" and "SRC emacs-lisp" too? :)
--
Kaushal Modi
ptures by mistake.
- In the event you want to copy something and deliberately kill the capture
buffer, you can always paste it with C-y M-y.
--
Kaushal Modi
On Wed, Oct 18, 2017, 5:20 PM Kaushal Modi <kaushal.m...@gmail.com> wrote:
>
> Thanks for the instructions, below works perfectly!
>
As a quick follow up, it's already implemented in ox-hugo:
https://ox-hugo.scripter.co/doc/source-blocks/#highlighting
Thanks again! :)
> --
Kaushal Modi
on the debug code I pasted earlier in this thread now
look like:
=
[src-block dbg] number-lines: nil
[src-block dbg] switches: nil
[src-block dbg] parameters: ":foo bar :hl_lines 1,3-4"
=
--
Kaushal Modi
r if a
non-intrusive change in Org code can still have the :parameters available
during export. Would it be possible to remove *only* babel-recognized
parameters and leave the unidentified parameters (which could be specific
to an exporter) intact?
--
Kaushal Modi
On Tue, Oct 17, 2017 at 8:51 AM Kaushal Modi <kaushal.m...@gmail.com> wrote:
> Hello,
>
> I am using the latest Org master.
>
> I am trying to retrieving user-set parameters for a source block. While I
> am able to retrieve the :switches property for the src-block eleme
no [3 times]
=
So it is clear that the parameters are read inside
org-element-src-block-parser, but I don't understand why
(org-element-property :parameters src-block) is unable to fetch the same.
Hints?
--
Kaushal Modi
:END:
Something
** Sub heading B
* Regular heading
Once again this is a regular heading and will appear numbered, and in the
TOC too.
** Sub heading C
--
Kaushal Modi
rse :) It's a bit difficult skimming through the code as I don't have
org-protocol set up.
> The code and/or documentation could be clearer
>
Would you like to submit a patch for that?
--
Kaushal Modi
that is embarrassing.. sorry for the trouble. That must have
sneaked in as I was trying that fontification to work through multiple
iterations..
Then remove the last zero-width space.
>
I just did.. (I need to now fontify zero-width space to prevent such
occurrences.)
--
Kaushal Modi
as example as in my first post).
Before this change:
- =title = "foo"= got fontified with org-verbatim face
- =title = "foo"= exported to `title = "foo" (C-c C-e t A)
After this change:
- =title = "foo"= does not get fontified with org-verbatim face (no Org
face is applied)
- =title = "foo"= exports to =title = "foo"= as it is (C-c C-e t A)
--
Kaushal Modi
On Thu, Oct 12, 2017 at 11:20 AM Kaushal Modi <kaushal.m...@gmail.com>
wrote:
> On Thu, Oct 12, 2017 at 11:01 AM Nicolas Goaziou <m...@nicolasgoaziou.fr>
> wrote:
>
>> Why do you consider it to be a regression? IIRC, the change allowed to
>> use zero-widt
ot work.
Also below does not work.
=title = "foo"=
(where is the unicode 0x200b inserted for ZERO WIDTH SPACE)
--
Kaushal Modi
'Saute' or 'saute'. How can I
> get it please?
1. You mean.. how to type that in Emacs in the first place?
2. Or it's fine in the Org file, but does not export correctly?
I can help if it's the first question.. just type "C-x 8 ' e" to get "é"
(and "C-x 8 ` e" to get "è").
--
Kaushal Modi
:url) (org-protocol-sanitize-uri (plist-get
parts :url
and title gets assigned value from a plist with key :title.
So that seems to match the documented: "The template refers to the data
through %:url and %:title placeholders.".
So I am surprised why %:link and %:description worked.
]])
Is that what you expected in the RESULTS?
Here is my relatively simply python setup where I default the interpreter
to python3:
https://github.com/kaushalmodi/.emacs.d/blob/master/setup-files/setup-python.el
and my minimal ob-python setup:
(use-package ob-python
:defer t
:config
(progn
(setq org-babel-python-command "python3"))) ;Default to python 3.x
--
Kaushal Modi
ause I was setting the
NEWLINE component in the org-regexp-emphasis component to a value greater
than the default of 1. It's on my list to get back to debugging that.
--
Kaushal Modi
On Tue, Oct 10, 2017 at 1:08 PM Kaushal Modi <kaushal.m...@gmail.com> wrote:
> I scanned through recent commits, but haven't yet figured out which commit
> affected this. Before I end up with git bisect, does anyone know a master
> branch commit that could have caused this?
>
scanned through recent commits, but haven't yet figured out which commit
affected this. Before I end up with git bisect, does anyone know a master
branch commit that could have caused this?
--
Kaushal Modi
LE
should be written instead
#+BEGIN_EXAMPLE
,* Headline
:PROPERTIES:
:header-args: :exports code
:header-args+: :var a=1 b=2
:header-args+: :var c=3
:END:
#+END_EXAMPLE
Please note that, however, old properties were defined at the source
block definition. Current ones are defined where the block is called.
--
Kaushal Modi
ended automatically,
correct
> but it used to work fine in the
> past. Flipping back to the older code for org-capture-expand-file
> works fine. So I'd say this is a bug!
>
As mentioned above, this is expected.
--
Kaushal Modi
pply only when you are exporting
that subtree.
Then it looks like, wrapping the table cell content in ~ is the only way.
--
Kaushal Modi
ree
> :PROPERTIES:
> :EXPORT_OPTIONS: *:nil
> :END:
>
--
Kaushal Modi
301 - 400 of 807 matches
Mail list logo
