From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Problem with agenda and diary
Date: Fri, 18 Mar 2011 00:43:25 +0100 [thread overview]
Message-ID: <8062rhs482.fsf@somewhere.org> (raw)
In-Reply-To: 9519.1300399599@alphaville.usa.hp.com
Hi Nick,
Nick Dokos wrote:
> =?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> wrote:
>> Side question: how do you do to see a really full backtrace?
>>
>> My backtraces always are elided with ellipsis inside the lines...
>>
>
> IIRC, these should do it:
>
> ,----
> | -- Variable: print-length
> | The value of this variable is the maximum number of elements to
> | print in any list, vector or bool-vector. If an object being
> | printed has more than this many elements, it is abbreviated with
> | an ellipsis.
> |
> | If the value is `nil' (the default), then there is no limit.
> |
> | (setq print-length 2)
> | => 2
> | (print '(1 2 3 4 5))
> | -| (1 2 ...)
> | => (1 2 ...)
> |
> | -- Variable: print-level
> | The value of this variable is the maximum depth of nesting of
> | parentheses and brackets when printed. Any list or vector at a
> | depth exceeding this limit is abbreviated with an ellipsis. A
> | value of `nil' (which is the default) means no limit.
> `----
Weird, they already both are at nil in my current setup.
As I don't play with them (in my config), I don't understand how the traces
are still partial...
Best regards,
Seb
--
Sébastien Vauban
next prev parent reply other threads:[~2011-03-17 23:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 13:30 Problem with agenda and diary Dan Griswold
2011-03-17 13:39 ` Erik Iverson
2011-03-17 13:48 ` Tassilo Horn
2011-03-17 14:45 ` Julien Danjou
2011-03-17 15:34 ` Tassilo Horn
2011-03-17 16:46 ` Julien Danjou
2011-03-17 20:28 ` Sébastien Vauban
2011-03-17 22:06 ` Nick Dokos
2011-03-17 23:43 ` Sébastien Vauban [this message]
2011-03-18 0:20 ` Nick Dokos
2011-03-18 10:07 ` Bastien
2011-03-17 14:48 ` Dan Griswold
-- strict thread matches above, loose matches on Subject: below --
2010-12-13 17:29 [PATCH] org: rework property set Julien Danjou
2010-12-13 21:21 ` Bernt Hansen
2010-12-14 9:01 ` Julien Danjou
2010-12-14 10:15 ` Giovanni Ridolfi
2010-12-14 10:30 ` Julien Danjou
2010-12-14 12:28 ` Bernt Hansen
[not found] ` <julien@danjou.info>
2010-12-14 14:50 ` Nick Dokos
2011-03-17 17:27 ` Re: Problem with agenda and diary Nick Dokos
2011-03-17 18:18 ` Tassilo Horn
2011-03-17 19:06 ` Dan Griswold
2011-03-17 19:45 ` Nick Dokos
2011-03-17 20:37 ` Dan Griswold
2011-03-17 22:01 ` Nick Dokos
2011-03-17 22:11 ` Nick Dokos
2011-03-18 10:36 ` Julien Danjou
2011-03-18 10:36 ` Julien Danjou
2011-03-18 14:04 ` Nick Dokos
2011-03-18 14:14 ` Nick Dokos
2011-03-18 14:56 ` Bernt Hansen
2011-03-18 15:20 ` Bastien
2011-03-18 15:33 ` Nick Dokos
2011-03-18 16:27 ` Julien Danjou
2011-03-19 10:20 ` Bastien
2011-03-19 10:20 ` Bastien
2011-03-18 14:22 ` Julien Danjou
2011-03-18 14:51 ` Julien Danjou, Nick Dokos
2011-03-18 15:05 ` Bastien
2010-12-16 13:34 ` Re: [PATCH] org: rework property set Carsten Dominik
2010-12-16 13:45 ` Julien Danjou
2010-12-16 13:55 ` Carsten Dominik
2010-12-16 17:12 ` Julien Danjou
2010-12-17 17:39 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8062rhs482.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).