lobal-cycling-at-bob-p t)
Also check outshine-speed-commands-default and outshine-speed-commands-user
(setup is similar to that of Org Speed Keys).
--
Kaushal Modi
gt; form an initial seed and a session number, that's be fabulous too.
>
I don't have a good idea on how to implement the date thing, but I see that
others have provided some input.
--
Kaushal Modi
/tiny-helper in here[1]) so that I don't have to remember the tiny
syntax. I still use tiny from time to time.
[1]:
https://github.com/kaushalmodi/.emacs.d/blob/master/setup-files/setup-tiny.el
--
Kaushal Modi
Maybe we eventually end up with 3 options (something like below):
- org-md-title-as-h1
- org-md-subtitle-as-h2
- org-md-heading-offset
WDYT?
(Side question: Would it be preferred to create a scratch branch on Org for
reviewing ox-hugo? Or would the GitHub repo mentioned above be fine?)
--
Kaushal Modi
On Wed, Aug 23, 2017, 9:46 PM Adam Porter wrote:
>
> That's very cool. Do you think Oleh would add it to Tiny?
>
Good question. I'll open an issue on that repo. When I wrote this, I wasn't
too good with git, creating branches or submitting PR's.
> --
Kaushal Modi
On Wed, Aug 23, 2017 at 9:46 PM Adam Porter wrote:
>
> That's very cool. Do you think Oleh would add it to Tiny?
>
PR submitted :) https://github.com/abo-abo/tiny/pull/9
--
Kaushal Modi
;t
break other Org functionality, would it be safe to add it before this
master cut? About this, would it be OK to start by creating a scratch
branch?
[1]: http://lists.gnu.org/archive/html/emacs-orgmode/2017-07/msg00292.html
--
Kaushal Modi
On Sat, Aug 26, 2017, 9:26 PM Nicolas Goaziou
wrote:
> Hello,
>
> Kaushal Modi writes:
>
> > I still have the org-set-tags refactoring[1] pending on my plate.
>
> Is there anything left to do? Do you need more time or can we merge it?
>
I need to create a new patc
'm using spacemacs if that helps.
>
> It sounds like an Emacs issue more than an Org one. You may want to
> report it to Emacs dev.
>
It would be better to email help-gnu-em...@gnu.org.
If you can recreate the issue in emacs -Q, you can even file a bug report
with steps to recreate the issue (M-x report-emacs-bug).
> --
Kaushal Modi
On Fri, Sep 1, 2017, 10:49 PM Adam Porter wrote:
> Kaushal Modi writes:
>
> > M-x list-load-path-shadows will also help. Pay attention to shadows on
> org packages.
>
> Wow, I did not know about that command. I have a bit of cleaning-up to
> do. :)
>
That&#x
On Sat, Sep 2, 2017, 10:23 PM Adam Porter wrote:
> Hi Eric,
>
> Thanks for doing this. I've had some similar code in my config for a
> while. I'll share some of it here in case you find it useful in doing
> this. You especially might find the org-read-structure-template
> function useful.
>
A
rg-mode.git/commit/?h=maint&id=7a29c82e1100f0e0e5c1c8d8b276139358abb031
--
Kaushal Modi
15
(bind-keys
:map org-mode-map
:filter (org-at-table-p)
("C-c ?" . org-table-field-info)
("C-c SPC" . org-table-blank-field)
("C-c +" . org-table-sum)
("C-c =" . org-table-eval-formula)
("C-c `" . org-table-edi
functions in a
package FOO to have FOO- prefix. Here[2] the discussion on that package's
GitHub issue thread.
PS: I believe it is the same case with ob- packages.
[1]: https://github.com/purcell/package-lint
[2]: https://github.com/purcell/package-lint/issues/89
Thanks.
--
Kaushal Modi
ables and
> functions. "ox" would be misleading.
>
Does this have to do with org-export--generate-copy-script (as discussed
here[1])? Is the prefix requirement for "org-" more widespread than that?
[1]: http://lists.gnu.org/archive/html/emacs-orgmode/2016-05/msg00231.html
--
Kaushal Modi
quot;
>
TIL about ALLTAGS and other Special Properties.
That org-split-string though needs the separator argument though, right?
(org-split-string (org-entry-get (point) "ALLTAGS") ":")
--
Kaushal Modi
in org-mode proper?)
>
I use a different approach to do the same thing using ox-gfm (based on a SO
solution). Look for orgtbl-to-gfm function here[1] and also my notes at
the end of that file.
[1]:
https://github.com/kaushalmodi/.emacs.d/blob/master/setup-files/setup-markdown.el
> --
Kaushal Modi
On Tue, Sep 12, 2017, 10:07 AM Kaushal Modi wrote:
>
> I use a different approach to do the same thing using ox-gfm
>
Correcting myself.. that solution has nothing to do with ox-gfm.
> --
Kaushal Modi
tent.
>
I was initially bummed by the same observation that William made too.. that
you now needed to first do C-c ` for editting shrunk cells. So thanks for
that C-c TAB tip. That workflow works for me.
--
Kaushal Modi
lin Baxter wrote:
> > I very much like the new table-column narrowing.
>
> +1
>
> Yesterday, I finally had the need/opportunity to use the new table
> column narrowing feature. Works very well. Thank you Nicolas!
>
> --
> : Eric S Fraga via Emacs 26.0.50, Org release_9.0.9-573-g09e612
>
--
Kaushal Modi
ul for Texinfo export, but defining
> it as a global macro makes Org documents a bit more portable across
> export back-ends.
>
For HTML too! :)
If there is any interest in it, I will add tests and documentation.
> I attach a proof of concept.
>
+1
Copying Oleh, as I believe he would also have some interest in this.
--
Kaushal Modi
Oh, and the reference to [1] that I forgot to paste..
[1]:
https://github.com/kaushalmodi/ox-hugo/blob/a486141e4e2c3f9f67e799e20af150611d77f850/ox-hugo.el#L535-L542
On Wed, Sep 13, 2017 at 10:03 AM Kaushal Modi
wrote:
> On Wed, Sep 13, 2017 at 9:23 AM Nicolas Goaziou
> wrote:
>
>&
On Thu, Sep 14, 2017 at 6:03 PM Nicolas Goaziou
wrote:
>
> > - HTML, MD :: as Kaushal points out, please use ..
>
> This is (almost) already the case.
>
Thanks. I tried the second version of the patch and it works great. About
the /almost/, the same .. export worked for MD e
On Fri, Sep 15, 2017, 8:54 AM Kaushal Modi wrote:
> On Thu, Sep 14, 2017 at 6:03 PM Nicolas Goaziou
> wrote:
>
>>
>> > - HTML, MD :: as Kaushal points out, please use ..
>>
>> This is (almost) already the case.
>>
>
> Thanks. I tried the secon
e TOC generation using the "toc:" option. Below does not
work at the moment, but would like that to work.
#+OPTIONS: num:nil H:4 toc:4
Thanks.
[1]:
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=bd2378161e76932103c9ef1f8343ffcc0d275007
--
Kaushal Modi
On Tue, Sep 19, 2017 at 10:49 AM Kaushal Modi
wrote:
> Can we enforce the TOC generation using the "toc:" option. Below does not
> work at the moment, but would like that to work.
>
> #+OPTIONS: num:nil H:4 toc:4
>
Above works after the below patch:
diff --git a/lisp
;t
mind if I need to set extra options/variables for that.
--
Kaushal Modi
: num:nil
No TOC will be exported (even though the org-export-with-toc default is t).
But if the file has:
#+OPTIONS: num:nil toc:4
As the toc value is a number, the TOC will be exported even though num is
nil.
--
Kaushal Modi
nd a certain level by doing
something like num:3, don't show headings beyond that level in the TOC. So
num:0 wouldn't number any heading and also not generate the TOC.
Now the 3rd use case (mine):
3. Unnumber all headings, but still keep them in TOC.
So allow this 3rd use case when, may be, we have num:nil and not num:0?
WDYT?
@Carsten: Does this satisfy your use case too?
> --
Kaushal Modi
On Wed, Sep 20, 2017, 4:14 AM Carsten Dominik wrote:
>
> I will go back and take a look at this thread. Can someone tell me what
> the subject line of that thread was?
>
http://lists.gnu.org/archive/html/emacs-orgmode/2017-09/msg00157.html
--
Kaushal Modi
other thread[1]. I have this exact use case. And if
the case 3 discussed in that thread is supported all should be good.
[1]: http://lists.gnu.org/archive/html/emacs-orgmode/2017-09/msg00497.html
--
Kaushal Modi
y clear what to expect in the exported formats.
> I also suggest to classify LaTeX issue as "wontfix".
> Any objection?
>
I don't use LaTeX exporter that heavily. If I do, I keep all headings
numbered and also in TOC. So I cannot yet grasp the LaTeX issue.
--
Kaushal Modi
r. So that needs to be escaped
with a backslash.
Try:
{{{date(%A\, %B %e\, %Y)}}
> --
Kaushal Modi
(:with-timestamps nil "<" org-export-with-timestamps)
(:with-title nil "title" org-export-with-title)
(:with-todo-keywords nil "todo" org-export-with-todo-keywords))
I believe that can be fixed by doing:
(:with-emphasize "WITH_EMPHASIZE" "*" org-export-with-emphasize)
.. and so on, and then one can have
:EXPORT_WITH_EMPHASIZE: t
or
:EXPORT_WITH_EMPHASIZE:
in the subtree property.
Is there a reason why this support wasn't added in the first place?
(Or does a method already exist to allow me to do the above?)
I can work on a patch if it's OK to enable this functionality.
--
Kaushal Modi
On Thu, Sep 28, 2017 at 1:28 PM Kaushal Modi wrote:
> .. and so on, and then one can have
>
> :EXPORT_WITH_EMPHASIZE: t
>
> or
>
> :EXPORT_WITH_EMPHASIZE:
>
> in the subtree property.
>
> Is there a reason why this support wasn't added in the first place
ushalmodi/ox-hugo/master/test/site/content/posts/export-without-emphasize.md
[3]: https://ox-hugo.netlify.com/test/posts/export-without-emphasize/
--
Kaushal Modi
:
>
> * Subtree
> :PROPERTIES:
> :EXPORT_OPTIONS: *:nil
> :END:
>
I didn't know that. This solves all the problems. Thanks.
--
Kaushal Modi
des gmane.org links which are now dead. I think
we should reference lists.gnu.org links (like above) for longevity of
references.
--
Kaushal Modi
On Fri, Sep 29, 2017 at 10:41 AM Kaushal Modi
wrote:
> Looks like this was an intended change:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=2b03e945a19701194e510791a96006c5eee9edc6
>
> Related discussion:
> http://lists.gnu.org/archive/html/emacs-orgmode/2016-10/msg00
EXPORT_OPTIONS: *:nil
> :END:
>
--
Kaushal Modi
On Sat, Sep 30, 2017, 1:44 AM Amos Bird wrote:
> Hi Kaushal,
>
> I did, it only works if I export the subtree instead of the whole buffer.
>
Yes, then I misunderstood. I thought you were trying to export just the
subtree. The EXPORT_* subtree properties apply only when you are ex
ically,
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
ritten 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
Org buffer.
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?
--
Kaushal Modi
On Tue, Oct 10, 2017 at 1:08 PM Kaushal Modi 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?
>
Hello,
I found the co
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
80885004301, 0.0], [0.0, 0.0, 5.4054]])
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
) (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..
I didn't dig deeper as to where the connection with org-protocol and
org-capture happens.
--
Kaushal Modi
aute'. 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
ork.
=title = "foo"=
(where is the unicode 0x200b inserted for ZERO WIDTH SPACE)
--
Kaushal Modi
On Thu, Oct 12, 2017 at 11:20 AM Kaushal Modi
wrote:
> On Thu, Oct 12, 2017 at 11:01 AM Nicolas Goaziou
> wrote:
>
>> Why do you consider it to be a regression? IIRC, the change allowed to
>> use zero-width space as a way to escape markup.
>
>
Also I spent few hou
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
ng.. 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
ifficult 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
nce again this is a regular heading and will appear numbered, and in the
TOC too.
** Sub heading C
--
Kaushal Modi
:hl 1,3-4 :eval 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
On Tue, Oct 17, 2017 at 8:51 AM Kaushal Modi 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 element,
> :parameters always retu
ge 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
s based 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
On Wed, Oct 18, 2017, 5:20 PM Kaushal Modi 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
- 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
org"?
Actually should the type string be matched only with "src org"? Because I
see the Org example blocks as blocks in HTML with no syntax
highlighting.. so those can contain code from any language.
Also as this is part of org and emacs, org-structure-predefined-blocks
deserves &quo
ert "\n"))
replacing that whole (if ..) form.
--
Kaushal Modi
a bit slow, honestly,
compared to using easy templates like "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
On Fri, Oct 20, 2017, 5:43 PM Kaushal Modi wrote:
> On Fri, Oct 20, 2017 at 5:15 PM Eric Abrahamsen
> wrote:
>
>> The template really only inserts the block type, not anything specific
>> like the source language or export backend.
>
>
> Right, but based on the cod
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
halmodi/ox-hugo/ ).
On Tue, Oct 24, 2017 at 12:36 PM Marcin Borkowski wrote:
>
> FWIW, I did something similar some time ago:
> https://github.com/mbork/org-one-to-many
>
--
Kaushal Modi
ber 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
ilog code blocks?
Probably the solution is to use noweb references with arguments? See the
Org manual.
> --
Kaushal Modi
quot;#"
#+END_EXAMPLE
Looks like that happens due to ~(insert "<>\n")~ when the
~org-macros~ ~noweb-ref~ has multiple lines. But I cannot figure out why
having
multiple lines is a problem.
** Section 1: {{{SEC_FOO}}}
#+BEGIN_SRC verilog :noweb yes
<>
parameter A = 1;
#+END_S
On Wed, Nov 1, 2017 at 11:51 AM Kaushal Modi 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 works:
1. Eval the =org-macr
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 wrote:
> I still don't have a fully working solution (see below). Hopefully someone
> can help figure out the reason for "Inv
sarily need the let form above, but that is in a form that
allows easily adding more languages in future.
--
Kaushal Modi
ank 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
On Sun, Nov 5, 2017 at 9:24 AM Kaushal Modi 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 changes the structure of
org-stru
On Mon, Nov 6, 2017 at 8:48 AM Nicolas Goaziou
wrote:
> I documented the two changes above in ORG-NEWS.
>
Thanks!
--
Kaushal Modi
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 "
--
Kaushal Modi
On Wed, Nov 8, 2017, 7:27 AM Kaushal Modi wrote:
> On Wed, Nov 8, 2017, 7:16 AM Bastien wrote:
>
>>
>> is there a simple mechanism in Emacs core to restore the same
>> functionnality?
>>
>
> +1
>
To clarify, I am not suggesting to blindly restore the ol
gt; 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
erved 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
On Thu, Nov 16, 2017, 8:35 AM Bastien Guerry wrote:
> Hi Kaushal,
>
> I can pull/push for org-mode and worg correctly, I'm not sure what
> could be wrong on the server, nothing changed in a while.
>
Thanks for checking.
Can you also check if my last commit failed worg bu
fault
(org-set-emph-re 'org-emphasis-regexp-components
org-emphasis-regexp-components)
=
[1]: https://i.imgur.com/6TmUoTS.png
--
Kaushal Modi
ted 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
s 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
ld still benefit from it
> being 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
en.
I have been building Emacs from emacs-26 branch pretty regularly and it's
very stable for my daily use.
Pretest download links:
For GNU/Linux systems:
ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-26.0.90.tar.xz
For Windows: http://alpha.gnu.org/gnu/emacs/pretest/windows/
Try it out! :)
> --
Kaushal Modi
On Fri, Nov 17, 2017 at 6:30 PM Nicolas Goaziou
wrote:
>
> You may want to test the following rules and report if it fits your use
> case.
>
That patch works great! Thanks!
--
Kaushal Modi
On Mon, Nov 20, 2017 at 10:42 PM Eric Thomas 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-lang and ox-reveal :)
--
Kaushal Modi
es), 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
ock
naming only when you want to call a Noweb block with an argument.
sorry for the noise
>
No worries.
> --
Kaushal Modi
i/org-mode.git/commit/?id=1d8126385cf979cfaade0e6a82040884bd6af56b
--
Kaushal Modi
On Mon, Nov 27, 2017 at 5:35 PM Nicolas Goaziou
wrote:
> Ouch! Fixed. Thank you.
>
Thanks! I confirm the fix.
--
Kaushal Modi
needs to
be a way for Org to figure out if the stuff following #+RESULTS is safe to
delete..
Can be probably have #+begin_results and #+end_results instead of
#+begin_example and #+end_example? And then process the
begin_results/end_results elements the same as example elements?
That way, we can safely 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 Tue, Nov 28, 2017 at 4:58 PM Kaushal Modi 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 have #+begin_results and #+end_res
fter #+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
isp
(message "Hello")
#+END_SRC
#+RESULTS:
: Hello
=
That's why I proposed earlier to wrap the Org generated results in
something like #+begin_results/#+end_results.
That way, Org is always sure that what it's deleting/overwriting is not
user-entered data.
The current behavior is risky, or at least should somehow be documented.
--
Kaushal Modi
On Fri, Dec 1, 2017 at 9:00 AM Kaushal Modi 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
(lambda ()
(
org-map-entries as soon as the first matching entry
is found?
- What's a better way to do the same?
Thanks.
--
Kaushal Modi
t EOL. The same issue is
with all emphasis variants: italics, code, verbatim.
--
Kaushal Modi
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
501 - 600 of 857 matches
Mail list logo
