emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: daniela-spit@gmx.it
To: Ihor Radchenko <yantar92@gmail.com>
Cc: tomas@tuxteam.de, emacs-orgmode@gnu.org
Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options
Date: Fri, 11 Dec 2020 15:47:05 +0100	[thread overview]
Message-ID: <trinity-8159839d-7e5e-4d9b-bc7e-3a727397bac0-1607698025865@3c-app-mailcom-bs06> (raw)
In-Reply-To: <871rfwctb2.fsf@localhost>



> Sent: Friday, December 11, 2020 at 3:26 PM
> From: "Ihor Radchenko" <yantar92@gmail.com>
> To: daniela-spit@gmx.it, tomas@tuxteam.de
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>
> > ... there is no active
> > hacking on org-agenda and adding new features.
>
> You are welcome to submit patches.
>
> I have experimental code to use pretty-symbols in agenda and align tags
> even when frame size changes [1]. However, last time I proposed this on
> mailing list, there was no interest...
>
> [1] https://orgmode.org/list/87r1v71aw0.fsf@localhost/

Was your patch welcomed?  Perhaps it is time to bring the topics again.
It could be that there are some criteria for patches to go on the
official version.  I have had times when I made comments and the problem
gets understood quite some time later.  At times it is wise to assume the
person reporting an encountered difficulty is aware of something you ain't.

It is- good to add patches, but at times people report something for the benefit
of everybody, not just themselves.  I should add that I resolved the problem
so have no need to argue how rude I can be.  We all know that there are many
in the community who lack social skills.  I went to one group meeting one time,
and buggered off in less than five minutes.

Regards
Daniela



  reply	other threads:[~2020-12-11 14:48 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 18:52 Emacs inserts hardwired org-agenda-files variable, overwriting user options daniela-spit
2020-11-29 20:07 ` Tom Gillespie
2020-11-29 20:19   ` daniela-spit
2020-11-29 21:01     ` Tom Gillespie
2020-11-29 21:02     ` Kyle Meyer
2020-11-29 22:08       ` daniela-spit
2020-12-11  3:59         ` TRS-80
2020-12-11  4:16           ` daniela-spit
2020-12-11  4:32           ` daniela-spit
2020-12-11  8:25             ` tomas
2020-12-11 13:47               ` daniela-spit
2020-12-11 13:59                 ` Detlef Steuer
2020-12-11 14:18                   ` daniela-spit
2020-12-11 14:23                   ` Christopher Dimech
2020-12-11 14:26                 ` Ihor Radchenko
2020-12-11 14:47                   ` daniela-spit [this message]
2020-12-12  2:35                   ` Jean Louis
2020-12-12  2:41                     ` daniela-spit
2020-12-13  5:19                       ` Jean Louis
2020-12-13  5:51                         ` daniela-spit
2020-12-13 13:19                           ` Jean Louis
2020-12-13 17:49                             ` Christopher Dimech
2020-12-13 20:28                               ` Jean Louis
2020-12-13  3:33                     ` TRS-80
2020-12-13  8:46                       ` Jean Louis
2020-12-13  9:28                         ` Ihor Radchenko
2020-12-13 17:31                           ` Jean Louis
2020-12-13 17:57                             ` Christopher Dimech
2020-12-13 17:59                             ` Christopher Dimech
2020-12-14 12:49                             ` Ihor Radchenko
2020-12-14 19:39                               ` Jean Louis
2020-12-11 14:43                 ` tomas
2020-12-11 14:54                   ` daniela-spit
2020-12-11 15:46                     ` tomas
2020-12-11 15:58                       ` daniela-spit
2020-12-11  6:25           ` Jean Louis
2020-11-29 20:15 ` Jean Louis
2020-11-29 20:46   ` daniela-spit
2020-11-29 20:58     ` Jean Louis

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=trinity-8159839d-7e5e-4d9b-bc7e-3a727397bac0-1607698025865@3c-app-mailcom-bs06 \
    --to=daniela-spit@gmx.it \
    --cc=emacs-orgmode@gnu.org \
    --cc=tomas@tuxteam.de \
    --cc=yantar92@gmail.com \
    /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).