Re: [O] TODO do not display in org-agenda mode
'spacemacs" is just a pre-configured version of emacs. I personally don't like spacemacs, but I have 'stolen' some of their configuration for my own setup. I find these pre-configured versions of emacs (spacemacs, prelude, better-defaults, Purcell's emacs.d, emagicians, etc) to be good references and a place for getting ideas, but just using them has a significant downside - you end up running an emacs configuration you don't really understand and are then at the mercy of others when it comes to problem diagnosis. Tim Neil Jerram writes: > Michaël Chlon writes: > >> Hi, >> >> I have spacemacs and write some org files. > > By the way, does anyone else find "spacemacs" bothering? Unlike > previous things like MicroEmacs, which have somehow always been clear to > me to be very different things from Emacs, I get the impression that > "spacemacs" users think that Emacs communities should be able to help > them in detail, which suggests that they think it's basically the same > thing. > > But if it's the same as Emacs, why use a different name that makes me > hesitate / worry over whether it might be different from Emacs? > > On the other hand, if it's different from Emacs, does it still make > sense to ask for support here? > > I'm genuinely in the dark here, although inclined to think that forking > the name (of Emacs) is a subtly damaging thing to do; so interested > either to be put right or to hear other opinions. > > Regards, > Neil -- Tim Cross
Re: [O] TODO do not display in org-agenda mode
Michaël Chlon writes: > Hi, > > I have spacemacs and write some org files. By the way, does anyone else find "spacemacs" bothering? Unlike previous things like MicroEmacs, which have somehow always been clear to me to be very different things from Emacs, I get the impression that "spacemacs" users think that Emacs communities should be able to help them in detail, which suggests that they think it's basically the same thing. But if it's the same as Emacs, why use a different name that makes me hesitate / worry over whether it might be different from Emacs? On the other hand, if it's different from Emacs, does it still make sense to ask for support here? I'm genuinely in the dark here, although inclined to think that forking the name (of Emacs) is a subtly damaging thing to do; so interested either to be put right or to hear other opinions. Regards, Neil
Re: [O] TODO do not display in org-agenda mode
Michaël Chlon writes: > Hi, > > I have spacemacs and write some org files. > But when I generate an agenda view for week, > for example, TODO task are not displayed !! What kind of agenda view do you mean? With 'C-c a a' (which is what I mostly use), TODO items are only shown by default if they have a date (scheduled or deadline or active timestamp). With 'C-c a t', all TODO items are shown. Hope this helps... Neil
[O] TODO do not display in org-agenda mode
Hi, I have spacemacs and write some org files. But when I generate an agenda view for week, for example, TODO task are not displayed !! Any idea what is wrong ? Here is my .spacemacs file: 8< -- >8 - ;; -*- mode: emacs-lisp -*- ;; This file is loaded by Spacemacs at startup. ;; It must be stored in your home directory. (defun dotspacemacs/layers () "Configuration Layers declaration. You should not put any user code in this function besides modifying the variable values." (setq-default ;; Base distribution to use. This is a layer contained in the directory ;; `+distribution'. For now available distributions are `spacemacs-base' ;; or `spacemacs'. (default 'spacemacs) dotspacemacs-distribution 'spacemacs ;; Lazy installation of layers (i.e. layers are installed only when a file ;; with a supported type is opened). Possible values are `all', `unused' ;; and `nil'. `unused' will lazy install only unused layers (i.e. layers ;; not listed in variable `dotspacemacs-configuration-layers'), `all' will ;; lazy install any layer that support lazy installation even the layers ;; listed in `dotspacemacs-configuration-layers'. `nil' disable the lazy ;; installation feature and you have to explicitly list a layer in the ;; variable `dotspacemacs-configuration-layers' to install it. ;; (default 'unused) dotspacemacs-enable-lazy-installation 'unused ;; If non-nil then Spacemacs will ask for confirmation before installing ;; a layer lazily. (default t) dotspacemacs-ask-for-lazy-installation t ;; If non-nil layers with lazy install support are lazy installed. ;; List of additional paths where to look for configuration layers. ;; Paths must have a trailing slash (i.e. `~/.mycontribs/') dotspacemacs-configuration-layer-path '() ;; List of configuration layers to load. dotspacemacs-configuration-layers '( ;; ruby csv python ansible javascript yaml scala imenu-list themes-megapack osx evil-commentary (geolocation :variables ;; geolocation-enable-automatic-theme-changer t geolocation-enable-location-service t geolocation-enable-weather-forecast t) ;; ;; Example of useful layers you may want to use right away. ;; Uncomment some layer names and press (Vim style) or ;; (Emacs style) to install them. ;; helm auto-completion better-defaults emacs-lisp git ;; markdown (org :variables org-enable-github-support t org-enable-reveal-js-support t org-projectile-file "TODOs.org" ) (shell :variables shell-default-height 30 shell-default-position 'bottom shell-default-shell 'ansi-term) spell-checking syntax-checking version-control react html ;; nginx ;; terraform search-engine ;; vim-powerline ) ;; List of additional packages that will be installed without being ;; wrapped in a layer. If you need some configuration for these ;; packages, then consider creating a layer. You can also put the ;; configuration in `dotspacemacs/user-config'. dotspacemacs-additional-packages '( flycheck anzu ;; org-bullets ) ;; A list of packages that cannot be updated. dotspacemacs-frozen-packages '() ;; A list of packages that will not be installed and loaded. dotspacemacs-excluded-packages '() ;; Defines the behaviour of Spacemacs when installing packages. ;; Possible values are `used-only', `used-but-keep-unused' and `all'. ;; `used-only' installs only explicitly used packages and uninstall any ;; unused packages as well as their unused dependencies. ;; `used-but-keep-unused' installs only the used packages but won't uninstall ;; them if they become unused. `all' installs *all* packages supported by ;; Spacemacs and never uninstall them. (default is `used-only') dotspacemacs-install-packages 'used-only)) (defun dotspacemacs/init () "Initialization function. This function is called at the very startup of Spacemacs initialization before layers configuration. You should not put any user code in there besides modifying the variable values." ;; This setq-default sexp is an exhaustive list of all the supported ;; spacemacs settings. (setq-default ;; If non nil ELPA repositories are contacted via HTTPS whenever it's ;; possible. Set it to nil if you have no way to use HTTPS in your ;; environment, otherwise it is strongly recommended to let it set to t. ;; This variable has no effect if Emacs is launched with the parameter ;; `--insecure' which forces the value of this variable to nil. ;; (default t) dotspacemacs-elpa-https t ;; Maximum allowed time in seconds to contact an ELPA repository. dotspacemacs-elpa-timeout 5 ;; If non nil then spacemacs will check for updates at startup ;; when the current branch is not `develop'. Note that checking for ;; new versions works via git commands, thus it calls GitHub services ;; whenever you start Emacs. (default nil) dotspacemacs-check-for-update nil ;; If non-nil, a form that evaluates to a package directory. For example, to ;; use different p
