[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#135: generate autoloads versus eval-expression-print-level (patch)
From: |
Lars Magne Ingebrigtsen |
Subject: |
bug#135: generate autoloads versus eval-expression-print-level (patch) |
Date: |
Sun, 10 Jul 2011 15:18:28 +0200 |
User-agent: |
Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) |
Andreas Schwab <schwab@linux-m68k.org> writes:
> That argument is actually a stream (which can be a function), though
> that doesn't help since that receives the individual characters instead
> of the form to print.
Ah, right. So that wouldn't work. But we could add a new optional
parameter to `eval-region' to do the suggested thing.
But is it worth it?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
- bug#135: generate autoloads versus eval-expression-print-level (patch), Lars Magne Ingebrigtsen, 2011/07/06
- bug#135: generate autoloads versus eval-expression-print-level (patch), Drew Adams, 2011/07/06
- bug#135: generate autoloads versus eval-expression-print-level (patch), Lars Magne Ingebrigtsen, 2011/07/07
- bug#135: generate autoloads versus eval-expression-print-level (patch), Stefan Monnier, 2011/07/07
- bug#135: generate autoloads versus eval-expression-print-level (patch), Lars Magne Ingebrigtsen, 2011/07/10
- bug#135: generate autoloads versus eval-expression-print-level (patch), Andreas Schwab, 2011/07/10
- bug#135: generate autoloads versus eval-expression-print-level (patch),
Lars Magne Ingebrigtsen <=
- bug#135: generate autoloads versus eval-expression-print-level (patch), Stefan Monnier, 2011/07/11
- bug#135: generate autoloads versus eval-expression-print-level (patch), Kevin Ryde, 2011/07/14
- bug#135: generate autoloads versus eval-expression-print-level (patch), Lars Magne Ingebrigtsen, 2011/07/15
- bug#135: generate autoloads versus eval-expression-print-level (patch), Kevin Ryde, 2011/07/16