2012ko irailak 16an, Moritz Ulrich-ek idatzi zuen:
> I get this error when I run `org-mobile-push'. Setting
> `debug-on-error' to t doesn't bring up an error buffer when I get this
> error.
>
> GNU Emacs 24.2.1 (x86_64-apple-darwin11.4.0, NS apple-appkit-1138.47)
> Org-mode version 7.9.1 (release
n any case. But
otherwise, it should be added to the hook’s documentation that any
changes to the agenda buffer could be turned into an error by a
read-only setting.
--
Aaron Ecay
-from-file, which asks the
user whether to really import very large files (or just ignores such
files)
2) adding a new :results handling header arg “really-silent” (probably
with a better name...) that discards the result entirely, not even
printing it to the minibuffer.
--
Aaron Ecay
an attempt to produce a patch implementing it. And I’ll take a crack
at error reporting in the minibuffer too.
--
Aaron Ecay
made customizable.
I also chose the polarity of the y-or-n-p so that picking the default
(yes) option does the sensible thing of not hanging emacs, although it
thus does discard data. I’m not sure which is the worse problem.
>From 1053f3acfc21f24fc994ae85adff6779838b0ce7 Mon Sep 17 00:00:00 20
le, this allows certain code to run that otherwise wouldn’t (at
least not without hacks, such as putting NULL at the end of an R source
block so that the “.Last.value” in the block is trivial).
--
Aaron Ecay
You need to escape the backslash inside the string, I think. "\1" is
interpreted as a string consisting of one character, the ASCII character
with hex code 0x01, which happens to be C-a. "\\1" is a 2-character
string: backslash, then one.
--
Aaron Ecay
, better way of getting the raw text
content of the special-block that doesn’t succumb to this problem.
Thanks in advance,
Aaron Ecay
org-bug.el
Description: application/emacs-lisp
* Intro
#+name: setup
#+begin_src elisp :results output :exports both
(+ 1 1)
#+end_src
foo
#+begin_foo
bar
Hi Sebastien,
2014ko ekainak 18an, Sebastien Vauban-ek idatzi zuen:
>
> Hi Aaron,
>
> Aaron Ecay wrote:
>> [...]
>> babel needs to fetch 30 properties per source block. Indeed, this is
>> marked “deprecated” in the source, in favor of a system where there is
>
rent name for this
variable now that it no longer holds a file name.
> (header (if (or (eq (nth 1 value) 'hline) colnames-p)
> "TRUE" "FALSE"))
> (row-names (if rownames-p "1" "NULL")))
> (if (= max min)
> - (format "%s <- read.table(\"%s\",
> + (format "%s <- read.table(textConnection('%s'),
This will fail if ‘file’ contains an apostrophe character. I guess you
need to escape apostrophes in ‘file’.
HTH,
--
Aaron Ecay
t;preamble")
| (org-babel-tangle)
| #+end_src
|
| #+name: preamble
| #+begin_src latex :tangle preamble.tex
| % code goes here
| #+end_src
`
You’ll need to use some combination of “:exports none” or a headline
tagged :noexport: to avoid these src blocks showing up in the exported
output.
HTH,
--
Aaron Ecay
Hi Daniele,
>
> Hello Aaron,
>
> Nice, since I do not use short caption, this could be really a
> viable solution.
>
> How I am supposed to set it up?
>
> I added it as:
>
> (add-hook 'org-mode-hook (lambda () (awe-org-setup-fill-hook)))
>
> When pressing M-q it does nothing on #+caption: lines.
>
might adapt to
increase the territory that falls within rather than outside the
Turing-complete boundary.
Just my 2 cents,
--
Aaron Ecay
lisp-mode, which is
kind of surprising to me – but I did not look very hard)
- make it easier to develop parts of org using these LP features.
Cheers,
--
Aaron Ecay
Hi Nicolas,
2014ko ekainak 21an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Aaron Ecay writes:
>
>> The first is that editing non-trivial latex code embedded in an elisp
>> string quickly becomes tedious, whereas it’s much pleasanter in org
>> using org-
2014ko ekainak 14an, Aaron Ecay-ek idatzi zuen:
>
> * contrib/lisp/org-mtags.el: Delete file.
> * lisp/org.el (org-structure-template-alist): Remove -style tags.
> (org-complete-expand-structure-template): Don't handle -style tags.
> ---
> contrib/
2014ko ekainak 21an, Aaron Ecay-ek idatzi zuen:
[...]
>> Eventually, if you insist on writing your full preamble within the
>> document, you can start to write it in a LaTeX-mode buffer, copy it in
>> your Org document and add "#+LATEX_HEADER: " in front of each lin
,
--
Aaron Ecay
f the above suggestions but otherwise the patch looks good
and I think it should be applied.
--
Aaron Ecay
export tests live in the file testing/lisp/test-ob-exp.el, so that’s the
spot to look for examples.
Have you heard back from the FSF about your copyright assignment?
Thanks for the patches,
--
Aaron Ecay
d_src
|
| #+RESULTS:
| : :exports none :results value
`
--
Aaron Ecay
e: xyz
| : hi
|
| #+begin_src emacs-lisp :var abc=xyz
| (concat "*" abc "*")
| #+end_src
|
| #+RESULTS:
| : *hi*
`
HTH,
--
Aaron Ecay
Hello,
In the latest checkout of master, I am seeing an infloop in
org-element-inlinetask-parser. This originates when that function
calls back into org-element-at-point to look for a property drawer,
which moves the point back before the beginning of the inlinetask and
then attempts to re-enter
Duh, forgot to include the list in this reply.
On Sun, Jul 13, 2014 at 10:50 PM, Aaron Ecay wrote:
> Hi York,
>
> It’s not a totally trivial problem from the LaTeX side. This stack
> exchange answer outlines what could be a solution:
> <http://tex.stackexchange.com/a/54240>
e second is to let-bind ‘org-latex-fragment-image-overlays’ to nil
in an advice around the ‘org-ctrl-c-ctrl-c’ function, allowing you to
still use the more convenient C-c C-c binding.
--
Aaron Ecay
ut it would be nice if org supported multi-valued properties.
It does, at least to a first approximation. Look at the functions
described in:
(info "(org) Using the property API")
I’m not sure how well this feature is integrated with agenda
search/filtering, though – maybe you should give it a try.
--
Aaron Ecay
83f1304a54502c42707b6a4ba347703f0992dd/lisp/ess-tracebug.el#L148>.
>
> Maybe the regex should be put in a defcustom.
Why? The current mismatch between babel and ESS seems like a bug, but
once that’s fixed I don’t see the use case for configurability here.
(But maybe you have something in mind...)
--
Aaron Ecay
rnating the position in a 3- to 6-month
rota.
--
Aaron Ecay
t other
elements of org syntax (not just src blocks) can have a valid #+header
(and indeed other affiliated keywords, like #+attr_latex), so the fix
probably should be more general.
--
Aaron Ecay
Hi Bastien,
2014ko uztailak 27an, Bastien-ek idatzi zuen:
>
> Hi Aaron,
>
> Aaron Ecay writes:
>
>> There’s a warning in the Org manual about using filladapt with org, but
>> I’ve never noticed any problems.
>
> Interesting -- was it always like
y / commit it.
>
> Regards,
>
> Mark
Thanks for the patch. It is committed (with light modifications).
--
Aaron Ecay
nd_src
>
> -> eval: Symbol's value as variable is void: *this*
The value of :post should be a babel call (in the same format as e.g. a
#+call line), not an elisp form. If babel sees something that looks
like elisp, it will attempt to ‘eval’ it when parsing the src block,
before *this* is bound (which happens only upon execution, after
parsing).
--
Aaron Ecay
gt; | bar
> | #+end_src
> `
>
You have an infinite regress. In order to compute the result of the
dblock-name block, we need to resolve each of its :vars, which includes
dblock-name, so we try to resolve the same block again...
Converting the second and third src blocks to example blocks (leaving in
place the #+names) gives what you seem to be aiming for.
--
Aaron Ecay
This introduces the change that the output no longer appears in the
session buffer, but I think that’s actually an improvement: we were not
previously echoing the commands to the buffer, such that the output
would show up “out of the blue” without any indication of how it got
there.
--
Aaron Ecay
rposes having the warnings in the #+RESULTS: block is helpful.
>
> And when revising code, having the errors in the #+RESULTS helps -
> especially if I have to put aside work in progress.
Hmm. Certainly, the previous behavior should be retained for now. In
the longer term, I’d like to see a system whereby R errors trigger elisp
errors. This is so that the execution of a whole document (subtree,
etc.) will be halted by the first error, rather than continuing what may
be a long series of commands that will not give valid output. What do
you think?
Thanks,
--
Aaron Ecay
ontents of the current table cell, which could then be followed with
M-w (kill-ring-save). This would be more general (since you can also
e.g. delete the contents of the cell after marking it), and also not
require more keystrokes (as long as you can find a binding of 3 keys or
less for the mark-cell command).
--
Aaron Ecay
o check the exact version of org that is
giving you this unexpected result?
#+BEGIN_SRC emacs-lisp
(org-version nil t)
#+END_SRC
Thanks,
--
Aaron Ecay
easy, based on the code sample/hint that Chuck gave).
What do you think of the approach broadly?
>From ea99c10d148f71e5384144728a5714ecc5ae47ca Mon Sep 17 00:00:00 2001
From: Aaron Ecay
Date: Sat, 16 Aug 2014 00:49:05 -0400
Subject: [PATCH] ob-R: overhaul handling of :output results type i
It may be that we want to move to using the evaluate
package in all cases, in which case this suggestion would be workable.
--
Aaron Ecay
e about how such regimes work and how org could work
with them, ideally from people who have direct experience with them.
Otherwise, it would be disappointing if the fear that an unidentifiable
somebody somewhere might not be able to install R packages derailed the
improvement of babel’s R support.
Thanks,
--
Aaron Ecay
cause the to-be-tangled code block is also under the headline with the
:noweb-ref property, it will try to include itself inside itself,
leading to an infinite regress. Adding a headline before the third code
block fixes the issue.
--
Aaron Ecay
must have been removed accidentally,
> since the code that checks this option is still there.) Here is a patch
> to re-introduce it.
>
This option was lost in commit 7a956c38, and indeed its removal looks
like an accident. I pushed your patch.
Thanks for your vigilance,
--
Aaron Ecay
escaping to special
characters like backslashes as you would if they were processed by org.
Hope this is useful,
--
Aaron Ecay
future. But that’s a bigger project...)
Sorry for the confusion,
Aaron
>From 8e327b373effb3690cfc0d8fec85b51704d1fb92 Mon Sep 17 00:00:00 2001
From: Aaron Ecay
Date: Thu, 21 Aug 2014 18:09:04 -0400
Subject: [PATCH] ox-beamer.el: Match latex backend in generation of \author.
* lisp/ox-beamer
branch" is more explicit.
Pushed.
Thanks,
--
Aaron Ecay
* lisp/ox-latex.el (org-latex-src-block): Support :float no with
caption for minted.
(org-latex-listings): Edit docstring to describe this usecase.
This takes advantage of the caption package’s \captionof command,
which allows to insert a caption (with autogenerated number and
\ref-able label) wit
* lisp/org-table.el (org-table-convert-region-max-lines): New
defcustom.
(org-table-convert-region): Use it.
This is useful primarily for babel results. If a large table-like
object is returned by a code block, this function will become bogged
down in trying to read it, and hang emacs (necessitat
2014ko abuztuak 19an, Achim Gratz-ek idatzi zuen:
>
> Aaron Ecay writes:
>> R is capable of installing packages to a user-specified directory,
>> without requiring root or any other special privileges. So IT cannot
>> literally prevent R users from installing their own
2 info)
> @@ -413,6 +418,7 @@ last statement in BODY, as elisp."
> (list body org-babel-R-eoe-indicator)
> "\n"))
> (inferior-ess-send-input)) "\n"
> + (concat "^\\([ ]*["
> org-babel-R-command-primary-prompt "+\\.][ ]?\\)+\\([[0-9]+\\|[ ]\\)") line)
I don’t think this does what you want it to: you’re inserting the
contents of the variable inside a regex character class (delimited by
[]).
See the patch I just sent
<http://mid.gmane.org/871ts7r4ho@gmail.com> for a different
approach.
--
Aaron Ecay
t about that.
>
> As I wrote, yes, I think it makes sense to do such a change.
FWIW, I also think the present behavior is too magical, and am in favor
of the proposed change.
--
Aaron Ecay
of gross hacks, so I’d much
prefer the evaluate-based approach if it can be made palatable.
>From afa24835f2a170c59a044dcf3bcf0ee765e8b568 Mon Sep 17 00:00:00 2001
From: Aaron Ecay
Date: Sat, 16 Aug 2014 00:49:05 -0400
Subject: [PATCH] ob-R: overhaul handling of :output results type in a sess
Hi Nicolas,
2014ko abuztuak 23an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Aaron Ecay writes:
>
>> * lisp/ox-latex.el (org-latex-src-block): Support :float no with
>> caption for minted.
>> (org-latex-listings): Edit docstring to describe this usecase.
Hi Nicolas,
2014ko abuztuak 23an, Nicolas Goaziou-ek idatzi zuen:
>
> Aaron Ecay writes:
>
>> It’s not adding any new functionality to the exporter,
>
> Well, it is, since "captionof" command doesn't exist in Org default
> packages.
I guess this was un
* lisp/org.el (org-buffer-property-keys): Only match real property
drawers.
This patch adds an org-element based check. Otherwise the following
triggers a bogus prompt to fix a malformed drawer on
typing M-: (org-buffer-property-keys)
* foo
(add-to-list 'org-capture-templates
'(
ing
./lisp/org-faces.el:610:(org-copy-face 'org-agenda-date 'org-agenda-date-weekend
./lisp/org-faces.el:719:(org-copy-face 'org-time-grid 'org-agenda-current-time
./lisp/org-faces.el:791:(org-copy-face 'mode-line 'org-mode-line-clock
./lisp/org-faces.el:793:(org-copy-face 'mode-line 'org-mode-line-clock-overrun
Thanks,
--
Aaron Ecay
Hi Nicolas,
2014ko abuztuak 24an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Aaron Ecay writes:
>
>> Why is the compatibility=false option needed? I can’t figure this
>> out.
>
> This is in my local copy of the minted manual, in "7 Known issues&qu
out the user’s prompt customizations (or lack
thereof) at all.
It’s taking a little bit for me to digest the discussion in that thread,
but I hope that if you can live with your local modifications a bit
longer you will be pleased with the end result.
--
Aaron Ecay
;org-vars")
> trick.
I’ll defer to your judgment.
Thanks again for the feedback and revised patch. I’ll try to get a few
tests written this weekend, and study the remote vs. local files
business.
--
Aaron Ecay
Hi Seb,
2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen:
[...]
> Does it have something to do with `ess-eval-visibly' not being respected
> (whose default is `t')?
Indeed, babel’s R support let-binds this variable to nil when evaluating
value-type results in a session.
--
Aaron Ecay
lanning info,
> if any. As a consequence, the code for this function will be different
> anyway. IOW, I wouldn't bother too much.
I see. Thanks for the explanation.
--
Aaron Ecay
e. I can’t tell if this
would fix your problem or not, but if it’s exclusive to the faces I
listed in my previous email the answer is probably “yes.”
--
Aaron Ecay
Hi Chuck,
Attached is a new version of the patch, including a few more tests. I
have one question:
2014ko abuztuak 28an, Aaron Ecay-ek idatzi zuen:
>> but the patch here uses on.exit(file.create(...)) to ensure that that
>> file is created. One hiccup (not sure if it exists in ma
o search “by-backend” in the mailing list archives for other
relevant examples.
Hope this is helpful,
--
Aaron Ecay
properties?
Something like (at the file level):
#+property: session *foo*
or (at the subtree level):
:PROPERTIES:
:session: *foo*
:END:
This will likely be easier than trying to do surgery on the header-args
property.
--
Aaron Ecay
er
than just a code comment. Possibly it should be un-deprecated.
Certainly I agree that the suggested replacement is less capable. Sorry
I can’t help more. Maybe Eric or Achim (who introduced the deprecation)
will comment.
--
Aaron Ecay
Hi Achim,
2014ko irailak 8an, Achim Gratz-ek idatzi zuen:
>
> Aaron Ecay writes:
>> Eric Schulte has said <http://mid.gmane.org/87wqce0w9n@gmail.com>
>> that the deprecation of this feature is “premature”. I didn’t realize
>> at the time that the deprecation w
assignment described at
<http://orgmode.org/worg/org-contribute.html#sec-2> before you run
out of lifetime eligibility for TINYCHANGEs (which is ultimately
controlled by the emacs core developers and/or FSF’s lawyers, but
it’s widely taken to be 15 lines or fewer).
--
Aaron Ecay
Hi Achim,
2014ko irailak 9an, Achim Gratz-ek idatzi zuen:
>
> Aaron Ecay writes:
>> Can you say more about the corner cases?
>
> It's been quite some time since I looked at this, but inline calls were
> quirky for instance since their point of call is ill-defined.
S
n of ‘org-babel-R-initiate-session’ in ob-R.el,
verify that the call to ‘ess-wait-for-process’ is present, and use C-M-x
to reevaluate the defun.)
Thanks,
--
Aaron Ecay
Hi Nicolas,
2014ko abuztuak 28an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Aaron Ecay writes:
>
>> The other application I can think of is to allow captioned images and
>> tables not to float. The LaTeX world is full of tutorials on how to
>> un-floa
alternative is adding the (macro . org-export-macro-warn) entry
manually to all the relevant backends, and relying on future backend
authors to do the same.
3. Should this even be implemented as part of the backend’s
translate-alist, or at a lower level?
Thanks,
--
Aaron Ecay
>F
o interconvert between the two formats, but I
think the greater structure of this proposal makes things easier for
babel authors. (Another way of thinking of the proposal is that it
treats description lists like two-column tables.)
What do people think?
Thanks,
--
Aaron Ecay
>From a7e01675f2c
way simplification of
the code might also be possible.
Let me know if you’re interested; I may be able to dig the old
half-patch out of a disused git branch somewhere. It may have bitrotted
some, but it may also be useful.
--
Aaron Ecay
le special case in the source block transcoder. The docstrings
seem to spell out the criteria for using one function vs. the other
well, so there’s little danger of confusion. Adding \phantomsection to
‘org-latex--wrap-label’ would also make them diverge further in their
internal workings.
Thanks,
--
Aaron Ecay
and last) call to org-macro-replace-all
3. in ‘org-export-as’, manually walk the parse tree after expanding
macros, and make sure no 'macro type objects are left
WDYT?
--
Aaron Ecay
’s worth it (to me) to try and
engineer an improvement to it in order to enable the babel feature.
WDYT?
--
Aaron Ecay
correctly; i. e., this content will fail to be syntax-highlighted, and
> the mark-up syntax will be exported in verbatim by the exporter.
You will need to change the variable org-emphasis-regexp-components; see
the documentation thereof.
--
Aaron Ecay
org-contribute.html#sec-2>.
--
Aaron Ecay
Hi again,
2014ko irailak 23an, Aaron Ecay-ek idatzi zuen:
>
> Hi Marco,
>
> Thanks for your patch. TINYCHANGES can only be smaller than 15 lines,
> though, and your patch has more than that (even if we discount
> boilerplate like the license notice). So you should probably
ile includes export from my perspective.
Indeed, that’s the direction that the next iteration of this patch will
move, motivated by your and Nicolas’s comments.
Thanks,
--
Aaron Ecay
Hi Seb,
2014ko irailak 23an, Sebastien Vauban-ek idatzi zuen:
>
> Hi Aaron,
>
> Aaron Ecay wrote:
>> 2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen:
>>> I think it's related to an Emacs bug (#16440) which I reported on the
>>> Org mailing li
ok to these functions, perhaps we should add
another branch to their conditionals which tries (lookup-key global-map
(this-command-keys)), and calls that function if it exists. The error
would be raised as before if there is no binding for the key in
global-map.
How’s your elisp? Would you feel up to trying to create such a patch?
--
Aaron Ecay
plicated.
>From f4abc5c57764fc36d7405be6b6c2f5cd63396d8d Mon Sep 17 00:00:00 2001
From: Aaron Ecay
Date: Tue, 23 Sep 2014 13:54:47 -0400
Subject: [PATCH] allow speed commands to have prefix args
* lisp/org.el (org-self-insert-command): Allow speed commands to be
invoked with prefix args.
---
lisp/org.el | 8 +---
Hi Tobias,
2014ko irailak 23an, Tobias Getzner-ek idatzi zuen:
>
> Hello Aaron!
>
> On Tue, 23 Sep 2014 13:03:06 -0400, Aaron Ecay wrote:
>
>> You will need to change the variable org-emphasis-regexp-components; see
>> the documentation thereof.
>
> Thank y
block buffer originated?
One approach might be to advise the vc commands like (pseudocode):
(defadvice vc-foo (around org-src activate)
(when (in-src-edit-p)
(org-edit-src-exit))
ad-do-it)
--
Aaron Ecay
ss doesn’t run the same hook.
Sounds like the best advice for the moment is “don’t use follow-mode
with org”. Maybe it’s worth adding to the section on package conflicts
in the manual?
--
Aaron Ecay
, it must be
> a console problem that I have. Does your patch work for you on the
> console too?
It seems to, yes. Can you test org mode (not outshine) in the console,
and verify that the original patch works for you there? If it doesn’t,
that needs to be resolved before the patch can be merged.
Thanks,
--
Aaron Ecay
Hi Dieter,
The link on the page you linked to is broken, but if you manually change
the URL to the following it works:
https://staff.fnwi.uva.nl/c.dominik/Tools/constants/constants.el
--
Aaron Ecay
#x27;.
> `
>
> ,
> | User-defined Speed commands
> | ===
> | t outshine-todo
> `
>
> I get:
>
> ,
> | ;; * ELISP SCRATCH
> `
>
> strange ...
Sounds like maybe the patch is not too well integrated into outshine. I
get expected behavior under these conditions in org.
--
Aaron Ecay
PhD candidate, Linguistics
University of Pennsylvania
Hi Rasmus,
2014ko irailak 23an, Rasmus-ek idatzi zuen:
> I think he did:
>
> Patch:
>> From: Marco Wahl
>
> Worg:
>> 14. Marco Wahl
...that’s in the section for tinychange contributors without papers on
file though.
--
Aaron Ecay
$_2$ | anatase | PBEsol | -2763.61 | 34.25 | 178.71 |
| TiO$_2$ | anatase | PBE| -2781.16 | 35.13 | 171.42 |
--
Aaron Ecay
de block. If you
must have the #+property line for other reasons, override the global
setting of :colnames yes with :colnames no on the source block.
--
Aaron Ecay
ESCRIPTION”) (unlike now, when they are lists of strings of
the form “TERM :: DESCRIPTION”).
It might be nice to handle nested lists somehow, if a sensible design
can be created, but it looks like babel just discards them currently.
So I propose to leave this unchanged, for the present at least:
#+name: data
- foo
- bar
- baz
- quux
- abc
#+begin_src emacs-lisp :var data=data
(pp-to-string data)
#+end_src
#+RESULTS:
: ("foo" "bar" "abc")
--
Aaron Ecay
For better or for worse, Bastien already installed this fix on master as
commit 44d8, in response to Kaushal’s earlier bug report on this
issue. See <http://mid.gmane.org/87oaw92y6s@bzg.ath.cx>.
The fix has not yet been merged to the release branch, so it won’t yet
show up in the ELPA version of org which Kaushal seems to be using.
--
Aaron Ecay
Hi Ken,
2014ko irailak 26an, Ken Mankoff-ek idatzi zuen:
> debug-on-error doesn't help because there isn't actually an error as far
> as I can tell. It is a bug, not an error. Nothing shows up in
> *Messages*
How about setting debug-on-quit and hitting C-g when the prompt s
about using edebug (info "(elisp) Edebug") to instrument that function
and then stepping through to see where the prompt is triggered?
--
Aaron Ecay
ally gets to a broad audience.
>
> Anyway, would there be problems, they would be very, very limited: face
> problems, that's all!
The patch is now pushed to master.
Thanks,
--
Aaron Ecay
Hi Thorsten,
2014ko irailak 23an, Aaron Ecay-ek idatzi zuen:
>> 2. when not edebugging, C-u 4 : seems to work in both Org and Outshine
>>
>> -> "All tags realigned to column 0"
>
> Good. :)
I pushed this patch to the master branch. Thanks for testing it out.
--
Aaron Ecay
Hi Nicolas,
Thanks for the feedback.
2014ko irailak 23an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Aaron Ecay writes:
>
>> Um...but the patch I sent works precisely by defining a macro translator,
>> which does get called for any unexpanded (because undefin
Hi Rasmus,
2014ko irailak 23an, Rasmus-ek idatzi zuen:
>
> Hi,
>
> Aaron Ecay writes:
>
>>> You have two options. Either report an error, as you suggested, or
>>> insert an obnoxious message in the output, e.g., "UNKNOWN MACRO", à la
>>>
1 - 100 of 514 matches
Mail list logo
