mlo | 8 Mar 11:59 2006
Picon

OMIT more than one day

Hi,

is it possible to specify more than one single day in an OMIT command?

I have a recurring event:

     67 REM Wed AT 14:30 DURATION 0:30 SKIP MSG The Message

and would like to say, that from Mar 6 'till Mar 22 this will not take place

thanks
  mlo
--

?- b;not(b).

Martin Stubenschrott | 14 Mar 23:54 2006
X-Face
Picon
Picon

Wyrd on black-on-white terminal

hi,

has anyone got a colorscheme of wyrd which is usable on a black text on white 
background terminal?

I played with the color options, but some parts still remain with a black 
background?

Also when specifiying 'white' I don't get a real  white but a (very) light 
gray. Is this a .Xdefaults issue, or is 'white' hardcoded to some gray value 
in wyrd?

regards,
--

-- 
Martin Stubenschrott

Paul Pelzl | 15 Mar 05:44 2006
Picon

Re: Wyrd on black-on-white terminal

On Tue, Mar 14, 2006 at 11:54:56PM +0100, Martin Stubenschrott wrote:
> has anyone got a colorscheme of wyrd which is usable on a black text on white 
> background terminal?
> 
> I played with the color options, but some parts still remain with a black 
> background?

Yeah, looks like I completely screwed up some of the coloring code.
I'll see what I can do about that for the next release.

> Also when specifiying 'white' I don't get a real  white but a (very) light 
> gray. Is this a .Xdefaults issue, or is 'white' hardcoded to some gray value 
> in wyrd?

'white' should be a reference to the standard white color for the
terminal, which you ought to be able to override in .Xdefaults.  It will
be less intense than the 'bold white' color, so text that is not
highlighted may end up looking a bit gray.

Paul

Martin Stubenschrott | 15 Mar 08:42 2006
X-Face
Picon
Picon

Re: Wyrd on black-on-white terminal

On Wednesday 15 March 2006 05:44, Paul Pelzl wrote:
> > I played with the color options, but some parts still remain with a black
> > background?
>
> Yeah, looks like I completely screwed up some of the coloring code.
> I'll see what I can do about that for the next release.

Oh cool, thanks.

> > Also when specifiying 'white' I don't get a real  white but a (very)
> > light gray. Is this a .Xdefaults issue, or is 'white' hardcoded to some
> > gray value in wyrd?
>
> 'white' should be a reference to the standard white color for the
> terminal, which you ought to be able to override in .Xdefaults.  It will
> be less intense than the 'bold white' color, so text that is not
> highlighted may end up looking a bit gray.

Ah, now I see, your white refers to 'color7' in .Xdefaults, not to color0 as I 
thought.
--

-- 
Martin Stubenschrott

Tildar | 17 Mar 15:13 2006
Picon

Re: OMIT more than one day

No, unfortunatly you cannot specify multple days with one omit command.

Martin Stubenschrott | 17 Mar 16:27 2006
X-Face
Picon
Picon

Re: Wyrd on black-on-white terminal

On Wednesday 15 March 2006 08:42, Martin Stubenschrott wrote:
> > 'white' should be a reference to the standard white color for the
> > terminal, which you ought to be able to override in .Xdefaults.  It will
> > be less intense than the 'bold white' color, so text that is not
> > highlighted may end up looking a bit gray.
>
> Ah, now I see, your white refers to 'color7' in .Xdefaults, not to color0
> as I thought.

Is there a chance to also specify the 'foreground' and 'background' colors in 
the colorsettings? Or some setting like 'transparent', that a specific item 
is just colored with the default background color of the term? This would 
also enable people who like fake transparent terminals (not that I like it) 
to see their wallpaper.
--

-- 
Martin Stubenschrott

Jason Stein | 20 Mar 14:30 2006
Picon

Periodic Reminders Using Omits

Our school uses a 6 day repeating schedule. I would like to create a reminder of what day it is. I need to omit weekends and specified school holidays. I tried something like
omit 5 sep #labour day
rem 31 aug 2005 skip *8 msg day 1
rem 01 sep 2005 skip *8 msg day 2
etc.
With the hopes that the next day 1 would occur on sep 9. I would much rather just omit weekends instead of using an 8 day cycle because it won't always work, but I could get that to work either. Any suggestions. BTW I am a first time poster, so please be patient if there is an answer in the archives. I couldn't find it.


7 bucks a month. This is Huge Yahoo! Music Unlimited
Tildar | 21 Mar 17:33 2006
Picon

Re: Periodic Reminders Using Omits

I'll Play with this and see what I can do, but it might be some time
befor I get it figured out.

On 3/20/06, Jason Stein <jason_t_stein@...> wrote:
>
> Our school uses a 6 day repeating schedule. I would like to create a
> reminder of what day it is. I need to omit weekends and specified school
> holidays. I tried something like
> omit 5 sep #labour day
> rem 31 aug 2005 skip *8 msg day 1
> rem 01 sep 2005 skip *8 msg day 2
> etc.
> With the hopes that the next day 1 would occur on sep 9. I would much rather
> just omit weekends instead of using an 8 day cycle because it won't always
> work, but I could get that to work either. Any suggestions. BTW I am a first
> time poster, so please be patient if there is an answer in the archives. I
> couldn't find it.

Daniel Graham | 24 Mar 17:40 2006

reminding of late events

I just ran across Mike Soulier's post in the remind-friends archive and
thought my solution might be useful.

First define:

    FSET float(y,m,d) trigger(MAX(realtoday(), date(y,m,d)))
    FSET due(y,m,d) "(" + (date(y,m,d)-trigdate()) + ")"

    REM [float(2006,4,1)] MSG File tax return [due(2006,4,15)]%

On or before April 1, the calendar for April 1 (only) will then display 

    File tax return (14)

and on or after April 2, the calendar for the current date (only) will display

    File tax return (d)

where d is the number of days remaining before April 15, e.g.

on April 13: File tax return (2)

on April 18: File tax return (-3)

Note that the reminder never appears on more than one date so it
won't clutter up your calendar.

-Dan
--

-- 
Daniel A Graham
Professor of Economics
Duke University
Durham, NC 27708-0097
919 660-1802

Paul Pelzl | 25 Mar 02:03 2006
Picon

Re: Periodic Reminders Using Omits

On Mon, Mar 20, 2006 at 08:30:14AM -0500, Jason Stein wrote:
> Our school uses a 6 day repeating schedule. I would like to create a reminder of what day it is. I need to omit
weekends and specified school holidays. I tried something like
>   omit 5 sep #labour day
>   rem 31 aug 2005 skip *8 msg day 1
>   rem 01 sep 2005 skip *8 msg day 2
>   etc.
>   With the hopes that the next day 1 would occur on sep 9. I would much rather just omit weekends instead of
using an 8 day cycle because it won't always work, but I could get that to work either. Any suggestions. BTW I
am a first time poster, so please be patient if there is an answer in the archives. I couldn't find it.
> 

My current belief is that there is no (reasonable) way to do this.

The only conceivable algorithm for laying out the calendar properly is
to scan through every date in your school calendar one-by-one, skipping
weekends and holidays as you go, and keeping track of a count of days.
Remind offers a SCANFROM option, which looks promising at first, but the
syntax for expressions doesn't seem to provide a way to do any extra
computation or manipulation of state variables while that scan is being
performed.

The lack of looping constructs doesn't help either.

I did manage to get this far:

   # globally omit whatever holidays you want
   OMIT 1 Jan
   OMIT 10 Mar

   # initialize the counter
   IF !defined("daycount")
      SET daycount 1
      PRESERVE daycount
   ENDIF

   # the counter loops through a six day rotation
   FSET _next_day(x) choose(x, 2, 3, 4, 5, 6, 1)

   # every day after Jan 1 could be a candidate for triggering, but
   # omits get skipped
   IFTRIG Jan 1 2006 *1 SKIP OMIT Sat Sun
      REM [trigdate()] MSG "Day [daycount]"
      SET daycount _next_day(daycount)
   ENDIF

This will work *only* if you force remind to scan through a complete
block of days starting on some date at or before the start of the
semester, e.g. "rem -s3 Jan 1 2006" or "rem Jan 1 2006 *90".

Best I can do, maybe this will inspire someone else to come up with a
solution.  If not, I think you're stuck doing the work yourself, and
writing down a different REM statement for each day.  (Or if you're
clever, you can probably use a variation on the above script to print
out a few months worth of REM statements for you.)

Paul


Gmane