Dear Galen.
I use Semantic linefeeds for a lot of my org files [...]
Thank you for the reference about Semantic linefeeds.
I didn't knew it, but used it something similar sometimes when
operating on complex sentences/paragraphs.
I created org list items as in Slf, one semantic nucleus per
On Mon, Aug 14, 2017 at 5:59 PM Tim Cross wrote:
>
> I was using fci, but found all sorts of problems when it comes to
> org-mode. In addition to the issue you mention, you will also find
'spurious' additional characters turning up in things like html exports
> of your org files.
I fixed that
I was using fci, but found all sorts of problems when it comes to
org-mode. In addition to the issue you mention, you will also find
'spurious' additional characters turning up in things like html exports
of your org files. I also started getting font-lock errors when I tried
to edit special block
> "William" == William Denton writes:
William> I was able to use git bisect (on master) to narrow down
William> where the problem started (for me, at least):
William> 27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4 is the first bad
William> commit commit 27466a38bcd6f5f3c6bd3c61b8ec
Hello,
I would like to ask if it is possible to preview latex blocks. Something
like this (replace EXPORT with SRC, if you wish):
#+BEGIN_EXPORT latex
\begin{align}
I_{0}
& > \max{(\lambda_{f}^{2})}
\\
& > 2^{2}
\\
I_{
Julien Cubizolles writes:
> Julien Cubizolles writes:
>
>> Kyle Meyer writes:
>>
>>
>>> Since you have the git repo set up and have a good/bad range, you can use
>>> git bisect to find the offending commit.
>
> I finally found the offending commit,
>
> it's commit 4f578a3f7fe193229adc239c93d698
On Wed, Aug 9, 2017 at 5:58 AM Rasmus wrote:
> There’s definitely some sort of issue...
>
> I guess this is for a local file?
Correct. I was testing it out only on an HTML file (local) exported from
org.
> I guess it needs to be publicly
> available. But it doesn’t seem to work all the tim
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
--
Hi,
for some reasons I need to control the visibility of individual entries
of my caldav calendars. I have implemented a small patch that passes the
`CLASS' propery to the iCalendar export:
https://github.com/keinstein/org-mode/pull/1
I'd like to have this patch integrated in the short term. It
On Mon, Aug 14, 2017 at 1:55 PM William Denton wrote:
> I was able to use git bisect (on master) to narrow down where the problem
> started (for me, at least):
>
> 27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4 is the first bad commit
> commit 27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4
> Author: Nicolas
Hi all,
I use [Semantic
linefeeds](http://rhodesmill.org/brandon/2012/one-sentence-per-line/)
for a lot of my org files, for which having a visual indicator of column
80 is useful. I'm currently using
[`fill-column-indicator`](https://github.com/alpaker/Fill-Column-Indicator)
for this, but t
I was able to use git bisect (on master) to narrow down where the problem
started (for me, at least):
27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4 is the first bad commit
commit 27466a38bcd6f5f3c6bd3c61b8ec9253d4dbf4e4
Author: Nicolas Goaziou
Date: Thu Jul 27 15:22:45 2017 +0200
Fix `org-str
Julien Cubizolles writes:
> Kyle Meyer writes:
>
>
>> Since you have the git repo set up and have a good/bad range, you can use
>> git bisect to find the offending commit.
I finally found the offending commit,
it's commit 4f578a3f7fe193229adc239c93d6983bcc030d41 org-agenda: Small
refactoring b
You could also prefix the link by a string holding (in ascii) the number of
bytes of the unencoded link.
But that makes raw/manual editing of an org file much harder.
2017-08-14 18:26 GMT+02:00 Neil Jerram :
> Except if your original string was "%org-9.0"...
>
> For this kind of approach to wor
Except if your original string was "%org-9.0"...
For this kind of approach to work, you generally need to prefix
everything; specifically included the cases that are _not_ encoded.
Regards - Neil
On 12/08/17 16:01, John Kitchin wrote:
I was thinking of something like how all PDF files start
Kyle Meyer writes:
> Since you have the git repo set up and have a good/bad range, you can use
> git bisect to find the offending commit.
I'm having trouble using setting it up. To go back to a previous state
using magit, I'm
* choosing a commit in the log view of magit-status
* magit-checkou
Hello,
Ken Mankoff writes:
> Is there a way to get variables into org-edit-special? Maybe by pre-pending
> C-u to C-c '?
The problem is not getting the variables into the remote editing buffer.
As you noticed, we would only need to remove the read-only status from
`org-babel-expand-src-block' o
17 matches
Mail list logo
