Hi Ian,
Ian Kelling writes:
> Testcase: 1 megabyte of text lines in an example block, drag the scrollbar to
> a
> location you haven't been to yet.
>
> It often freezes for a few seconds, and doing things while its frozen like
> scrolling more can quickly make it freeze for a minute or so. Remo
James Harkins writes:
> After 243 commits to a constellation of org files, producing 10849
> lines of LaTeX code from the Beamer exporter, which render into 229
> pages of beamerarticle print-ready material, including 156 captioned
> code listings (and a handful of un-numbered ones) and 27 pages
Thanks!
On Sat, Mar 22, 2014 at 1:32 AM, Bastien wrote:
> Hi Konstantin,
>
> Konstantin Kliakhandler writes:
>
> > It appears that org-mode produces invalid latex code. An example
> > follows.
>
> Fixed, thanks,
>
> --
> Bastien
>
Hello,
Bastien writes:
> Konstantin Kliakhandler writes:
>
>> It appears that org-mode produces invalid latex code. An example
>> follows.
>
> Fixed, thanks,
I don't think this is the right fix. IIRC, I replaced "\ul" with
"\uline" a while ago for some reason (maybe a problem with newline
or
Hello,
Christopher Witte writes:
> I'm getting a weird problem with orgmode and flyspell mode. Using the
> latest version of org from git, open the attached file test.org and run M-x
> flyspell-mode, emacs will lock up. It has something to do with tables.
>
> Alternatively, make a new (empty) or
Hi Nicolas,
Nicolas Goaziou writes:
> I don't think this is the right fix. IIRC, I replaced "\ul" with
> "\uline" a while ago for some reason (maybe a problem with newline
> or unicode, I cannot remember). This would go backwards.
>
> There are probably other solutions (e.g., remove all underlin
Samuel Wales writes:
> here is the fix for bug #3:
There was a fix for this in master by Aaron.
I assumed you were reporting errors on master.
I've now cherry-pick the fix to maint, since
it's a fix.
If you find other problems, please first test
the master branch to check if they have been
fixe
Hi Ian,
the idea behind the patch looks good, although the patch needs
some clean-up (adding a Changelog entry, fixing the typos in the
docstring, etc.)
Also, the patch goes beyond the 15 lines: we cannot accept it
until you sign the FSF copyright assignment. If you're willing
to do this, please
On 03/22/2014 01:45 AM, Bastien wrote:
> Hi Ian,
>
> the idea behind the patch looks good, although the patch needs
> some clean-up (adding a Changelog entry, fixing the typos in the
> docstring, etc.)
>
> Also, the patch goes beyond the 15 lines: we cannot accept it
> until you sign the FSF copy
aha. yes, that's it. thank you.
Hi Ian,
Ian Kelling writes:
> I'd be happy to clean it up if there is interest in merging it. Also I've
> done the
> FSF paperwork a while ago, I'm just waiting on hearing confirmation.
Was it more than a month ago? If so, I'll ping them.
Let's wait for Eric's answer about whether the patch
> Was it more than a month ago? If so, I'll ping them.
We've been in email contact less than a week ago. It shouldn't be too long.
Ian Kelling writes:
> We've been in email contact less than a week ago. It shouldn't be
> too long.
Okay, this takes usually up to 6 weeks, so don't hold you breath!
--
Bastien
Excluding special entities would not interfere with anything I've done
with radio targets so far. I can imagine future uses, but probably
nothing I couldn't work around with Unicode.
But is this only about special entities, or about all Org syntax,
including subscripts/superscripts, emphasis...?
Hi Ian
On Sat, Mar 22, 2014 at 4:59 AM, Ian Kelling wrote:
> I use babel mostly for shell scripts. I wrote a patch to allow toggling the
> handling of errors & std err. I prefer standard error just get printed with
> everything else, the same as calling a script from a terminal. Doing this
> pro
hi, all
I Using org to Blog with Jekyll.
I want to get a right link to link to blog server's relative path after
publishing, the following is corressponding setting and source:
1. .emacs snippet
("org-static-dillon"
:base-directory "/study/doctor/note/org"
:base-extensi
On 03/22/2014 02:43 AM, Michael Brand wrote:
>
> For two reasons I would much prefer if there would be not yet another
> variable org-* but a header argument or a new value for e. g.
> ":results":
> - When someone would use org-babel-use-error-buffer then sharing Org
> source blocks would be les
Hello,
Christian Moe writes:
> But is this only about special entities, or about all Org syntax,
the latter.
> including subscripts/superscripts, emphasis...? That would be
> limiting. As long as radio targets are visible parts of the text, I'd
> like them to continue supporting such markup.
Bastien writes:
> Yes, maybe there is a better fix.
>
> If you can find why you used \uline instead of \ul that will help
> spot possible problems with the current fix, of course.
>
> I'm not for getting rid of the problem before we can tell for sure
> why the current solution is wrong.
This co
Hello,
Marcin Borkowski writes:
> I started to wonder and came to the conclusion that this might be
> interesting for my "cloze" idea (with syntax as in one of my previous
> messages). However, I can't really understand what is going on here.
> It seems to me that the key function is
> org-late
Nicolas Goaziou writes:
> Bastien writes:
>
>> Yes, maybe there is a better fix.
>>
>> If you can find why you used \uline instead of \ul that will help
>> spot possible problems with the current fix, of course.
>>
>> I'm not for getting rid of the problem before we can tell for sure
>> why the
Nicolas Goaziou writes:
> This comes from commit 4fc03ec1fe23c6ddccffaa064a282b258ca8b6b8.
>
> See thread at:
>
> http://comments.gmane.org/gmane.emacs.orgmode/67741
If it matters, I think that it would be preferable to solve it in a way that
exports the intended emphasis, rather than deletes i
Hello,
Konstantin Kliakhandler writes:
> If it matters, I think that it would be preferable to solve it in a way that
> exports the intended emphasis, rather than deletes it (although I'm not
> sure how to acheive thise).
>
> Surely there is a latex command that underlines stuff inside section
>
Hi Nicolas,
Nicolas Goaziou writes:
> It is technically possible to use \underline (hard-coded) in sections
> and \uline (or whatever is defined in`org-latex-text-markup-alist')
> everywhere else.
>
> Is there any downside to this proposal?
I don't know but it looks good to me, because the shor
Bastien writes:
> I don't know but it looks good to me, because the shortcomings of
> \underline not being able to wrap are not a problem for sections.
Here is the patch. b399ff0cba2382bf52d5bb6ef2b4a776fe0ac902 needs to be
reverted first.
Regards,
--
Nicolas Goaziou
>From 7a6bcad9dea5dd8a7c
Hello,
Jambunathan K writes:
> [RFC] Creole-style / Support for **emphasis**__within__**a word**
>
> The attached files should speak for themselves. Such an arrangement
>
> a) Does not change the status quo AT ALL.
> b) Provide more rope.
>
> The patch is in the spirit of "show and tell". I wi
Nicolas Goaziou writes:
> Here is the patch. b399ff0cba2382bf52d5bb6ef2b4a776fe0ac902 needs to be
> reverted first.
Please go ahead, thanks,
--
Bastien
Bastien writes:
> Nicolas Goaziou writes:
>
>> Here is the patch. b399ff0cba2382bf52d5bb6ef2b4a776fe0ac902 needs to be
>> reverted first.
>
> Please go ahead, thanks,
Done.
Regards,
--
Nicolas Goaziou
Hi Nicolas,
Nicolas Goaziou writes:
> In a nutshell, I don't think this will go past the active
> "backward-compatibility" squad on the ML. What we're really after is
> a way to
>
> - keep single character markup ;
> - get rid of `org-emphasis-regexp-components' ;
> - allow midword markup.
Hi all,
Bastien writes:
[ ...]
>
> Also, there is no "backward-compatibility squad", only users who care
> about what they like.
I have been part in threads that discuss backward-compatibility. As it
looks, there is the feeling that this ML is too(?) much concerned about
backward-compatibilit
Hi Andreas,
I'm also in favor of breaking backward compatibility when
it benefits Org's users and developers.
We should not consider changes only in terms of backward
compatibility, we should also consider them by themselves.
What I like with *this markup* is that it's non-intrusive:
it's easy t
Bastien writes:
> What I'm after is a bit different:
Is it?
> - keep single character markup;
>
> - simplify `org-emphasis-regexp-components' (getting it of it is the
> extreme version of simplifying it);
You call it extreme, I label it ambitious.
Also, "getting rid of it" really means "no
Nicolas Goaziou writes:
> You call it extreme, I label it ambitious.
>
> Also, "getting rid of it" really means "no need to change it anymore".
> I'd rather have a static complex regexp than a simple customizable one
> for the sake of syntax consistency. Of course, a fixed simple regexp is
> bett
Hello Bastien,
Bastien writes:
> Just add a missing full-stop at the end of the Changelog sentence "in
> its own section.",
Done
> and perhaps use `C-x 4 a' from within the diff to
> include the section's name in the Changelog too.
I tried that in both parts of the diff, but then I get :
Thank you for sharing.
We all benefit greatly from others monumental efforts of others.
Thanks, to them.
On Fri, Mar 21, 2014 at 11:58 PM, James Harkins wrote:
> After 243 commits to a constellation of org files, producing 10849 lines
> of LaTeX code from the Beamer exporter, which render into
On Sat, Mar 22, 2014 at 4:31 PM, Grant Rettke wrote:
> Thank you for sharing.
>
> We all benefit greatly from others monumental efforts of others.
>
> Thanks, to them.
>
>
> On Fri, Mar 21, 2014 at 11:58 PM, James Harkins
> wrote:
>>
>> After 243 commits to a constellation of org files, producing
Hi Nicolas,
Nicolas Richard writes:
> Done
Thanks, applied on master, with a slight change in the Changelog
entry.
--
Bastien
Nicolas Goaziou writes:
> It is technically possible to use \underline (hard-coded) in sections
> and \uline (or whatever is defined in`org-latex-text-markup-alist')
> everywhere else.
>
> Is there any downside to this proposal?
Disclaimer : While I do use LaTeX, I rarely use the exporter, and ne
Bastien writes:
> Thanks, applied on master, with a slight change in the Changelog
> entry.
Ok thanks. For my information, did C-x 4 a work for you in adding the
section name or did you add it manually ?
--
Nico.
Hi Bastien,
> The indentation of the exported HTML looks correct to me:
> "some text" is right below "*** Third level"
> The HTML color of the leading stars is taken from the org-hide face.
> When your background is black, the org-hide face is black, hence the
> color you see in the HTML output.
I would really like to see the resulting paper too!
On Sat, Mar 22, 2014 at 5:35 PM, Dave Taht wrote:
> On Sat, Mar 22, 2014 at 4:31 PM, Grant Rettke
> wrote:
> > Thank you for sharing.
> >
> > We all benefit greatly from others monumental efforts of others.
> >
> > Thanks, to them.
> >
> >
>
Aloha Nick,
Nick Dokos writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha Nick,
>>
>> Nick Dokos writes:
>>
>>> #+BIND is supposed to bind the variable *during export*. The test is to
>>> run the export and see if the hyperref stuff is gone from the tex file.
>>>
>>> Nick
>>
>> I did r
Nicolas Richard writes:
> Nicolas Goaziou writes:
>> It is technically possible to use \underline (hard-coded) in sections
>> and \uline (or whatever is defined in`org-latex-text-markup-alist')
>> everywhere else.
>>
>> Is there any downside to this proposal?
>
> Disclaimer : While I do use LaTe
Hello,
On Mar 22, 2014 7:06 PM, "Nicolas Richard"
wrote:
> I'd go even a little further : assuming it makes sense to underline
> within a section header, does it also make sense to propagate that
> formatting to the toc and/or header of the document ? If not, I suggest
> exporting as:
> \section[
On Sat, Mar 22, 2014 at 08:52:11AM +0100, Bastien wrote:
> James Harkins writes:
>
> > After 243 commits to a constellation of org files, producing 10849
> > lines of LaTeX code from the Beamer exporter, which render into 229
> > pages of beamerarticle print-ready material, including 156 captione
Dnia 2014-03-22, o godz. 16:30:31
Nicolas Goaziou napisał(a):
> > Also, there is no "backward-compatibility squad", only users who
> > care about what they like.
>
> That is what they want us to believe! :)
Ninja'd!
Re: topic: one idea that is maybe not very Org-ish, but seems
reasonable: Org
* contrib/lisp/org-mac-link.el (org-as-mac-chrome-get-frontmost-url):
Improve AppleScript used for grabbing information from Chrome. Now
it's shorter and doesn't require switching to the app. Also,
starting and ending quote are trimmed only when necessary.
---
contrib/lisp/org-mac-link.el |
one option might be to keep what we have for emphasis, ossify it, and
create a backend-independent nestable, multiline [and so on] markup
for emphasis.
but not just any syntax [because that would clutter us with more
syntax]. this time it would be $[extensible :pretty-nicely t], and it
will work
Bastien gnu.org> writes:
>
> Hi Brady,
>
> Brady Trainor uw.edu> writes:
> > (when respect-content
> > (and (looking-at "[ \t]+") (replace-match ""))
> > I thought to try substituting "[ \t]+" with "[\t]+", and byte compiled the
> > file. But this did not solve.
> What you w
49 matches
Mail list logo
