The point is that sometimes there are brief exceptions to recurring alarms.

I've had the same need as the OP. Alarm needs a temporary suspend feature.

Were you Finns taught "double-negative english" in school, or are you just messing with my head?

*waves hand*
These are not the answers you are looking for.

Out of interest has no one thought of the simple solution to this. Remove the battery! *puts tinfoil hat on* Unless... they built an internal battery in so it could still annoy the bajesus out of you.

Actually, I have learned that mCalendar alarms do respect the audio mute settings. Of course, setting said alarms is a little clunky. But, they do come on even if mCalendar is not running - same alarm window as regular alarms, but they stay shut up if told to do so. Must be some kind of setting in the actual alarm entry. Now, if we could figure that out, then the app to change it back and fourth would be pretty easy, I expect. I might even have a go at it myself in Perl.

As for the rest, yeah, removing the battery is, literally, the drop-dead solution.

David...

BTW, Seqretary has a setting under Preferences | Sound; "Play sound even if muted". Turning that off and starting to use Seqretary not be the best/easiest way to solve your need, but if we're talking "remove the batteries", this might as well be mentioned too.

Ideas:

Cut the plug off a old headphone and you have a physical "mute" token that you can plug into your tablet whenever it should be silent. Although it does not seem to work with alarms.

Edit: killing alarmd does not help - it is restarted right away. https://garage.maemo.org/projects/alarmd/ might be a good starting point, although the source does not seem to be available.

It seems like there is work ongoing to open source the alarmd code: https://bugs.maemo.org/show_bug.cgi?id=3635

In the mean time, you could file a feature request in Maemo Bugzilla

Edit 2: After reading the rest of this thread, I really wonder why I haven't thought about looking for an initscript for alarmd before. Anyway.. that's the way to go (see some posts below for how to do it .

This is a conceptual problem that has a very simple theoretical solution: "Just don't set the alarm in the first place.". Unfortunately, real life doesn't work like that Well, unless you lead a very robotic life or a hermit or something.

It's common enough that some phones have a hardware switch to disable audio (usually also gives the option to reroute the notice/alarm to buzz/vibrate): Treo 6xx, iPhones.

How about this:
http://talk.maemo.org/showthread.php?t=33899

it's not a secret at all that alarms rely on the OSSO Alarm Daemon. This daemon can be managed via a usual (for linux users at least ) init script. You can disable the alarm daemon by opening a terminal, become root and use
alarms won't go off then and of course you also won't be able to set a new timer. To re-enable the alarm daemon: (again from a root terminal)
Hope this helps!
mtron