From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode v8 broke my workflow
Date: Sat, 18 May 2013 17:16:33 +0200 [thread overview]
Message-ID: <20130518171633.037307ce@aga-netbook> (raw)
In-Reply-To: <51977D7F.2040408@easy-emacs.de>
Dnia 2013-05-18, o godz. 15:09:19
Andreas Röhler <andreas.roehler@easy-emacs.de> napisał(a):
> Am 18.05.2013 13:54, schrieb Marcin Borkowski:
> > Dnia 2013-05-18, o godz. 08:07:07
> > Andreas Röhler <andreas.roehler@easy-emacs.de> napisał(a):
> >
> >> Am 18.05.2013 00:52, schrieb Marcin Borkowski:
> >>> Hi list,
> >>>
> >>> can't resist;): http://xkcd.com/1172/
> >>>
> >>> I have this at the end of my .emacs:
> >>>
> >>> (setq inhibit-splash-screen t)
> >>> (org-agenda-list)
> >>> (delete-window)
> >>>
> >>> The point is that I want agenda to appear as the only thing when I
> >>> start Emacs. However, sometimes I start it e.g. when delivering a
> >>> presentation; I don't want all the people to look at my overdue
> >>> todo items;), so I used to press q while Emacs was starting
> >>> (which takes quite a while on my netbook). This used to bury the
> >>> agenda so that *scratch* was visible. Now, instead of *scratch*,
> >>> one of my agenda org files appears. What do I do to restore the
> >>> previous behavior? (Really, that setup worked for me;).)
> >>>
> >>> Best,
> >>>
> >>
> >> You could move (org-agenda-list) at the beginning of your init, so
> >> it's not displayed as last. However, it might be displayed while
> >> loading for a short time though. If you want make sure it's never
> >> shown, don't see another way than deleting it from init and call it
> >> via M-x, resp. from menu.
> >
> > I guess you misread my post;
>
> Probably
>
> the problem seems to be about the order of
> > buffers - I' like all the .org buffers to be /buried/.
> >
>
> Okay. As it seems to matter at start, what about not open it?
Well, org-agenda-list visits all agenda files and is quite angry if
their buffers get killed.
> In cases, you might want open some files only ocassionaly, you could
> put a command into your init.
>
>
> (defun load-my-stuff-please ()
> (interactive)
> (load "/PATH-TO-STUFF/STUFF-1")
> (load "/PATH-TO-STUFF/STUFF-2")
> ...
> (load "/PATH-TO-STUFF/STUFF-n"))
>
> After evaluation resp. restart may you call it as command.
> Also, if want to load it all the time, add to your init
> after this definition
>
> (load-my-stuff-please)
Well, load won't work for me - these are not Lisp files.
Regards,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
prev parent reply other threads:[~2013-05-18 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 22:52 Org-mode v8 broke my workflow Marcin Borkowski
2013-05-18 6:07 ` Andreas Röhler
2013-05-18 11:54 ` Marcin Borkowski
2013-05-18 13:09 ` Andreas Röhler
2013-05-18 15:16 ` Marcin Borkowski [this message]
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=20130518171633.037307ce@aga-netbook \
--to=mbork@wmi.amu.edu.pl \
--cc=emacs-orgmode@gnu.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).