the podcast was autgenerated with NotebookLLM - no human intervention.
Link: jmp.sh/EfQ7tav4
submitted by /u/pmz
[link] [comments]
Hello everyone. We are writing a little script that sends a mail to a collegue or department in case of sickness. We have a website that we host that can also be accessed remote with a form to fill out.
Our problem is after trying some things that the Mail arrives with no Subject. The subject is always empty and we dont understand why. Any idea? Here is most of the Script:
if (eingabefehler() == 1) {
print $cgi->header(),
$cgi->start_html('Krankmeldung nicht abgeschickt!'),
$cgi->h1('Bitte alle Eingabefelder ausfüllen');
print $cgi->end_html();
}
else {
$abt = $cgi->param('abt');
$smtp = Net::SMTP->new('cluster.xx.xx',Timeout => 30);
$smtp->mail($ENV{USER});
switch($abt)
{
case "xx" { $smtp->to('mail.address'); )
}
$smtp->cc('mail.address');
$smtp->mail($ENV{USER});
$smtp->data();
$smtp->datasend("From: Krankmeldeformular\n");
switch($abt)
{
case "xx" { $smtp->datasend("To: person"); }
}
$smtp->datasend("Subject: Krankmeldung\n");
$smtp->datasend("\n");
$smtp->datasend("Name: ",$cgi->param('name'),"\n\n");
$smtp->datasend("Datum: ",$cgi->param('datum'),"\n\n");
switch($abt)
{
case "xx" { $smtp->datasend("department \\n\\n"); }
}
$smtp->dataend();
$smtp->quit;
print $cgi->header(),
$cgi->start_html('Krankmeldung abgeschickt!'),
$cgi->h1('Mail versendet');
print $cgi->end_html();
}
submitted by /u/Lionsrise
[link] [comments]
Planning to replace my frontend with VueJs, looking for tips from those who have done it and some advice.
Its unclear to me how the templating or communication between Perl and VueJs woild work, dpes Vue get setup in my root directory and how does my backend communicate with the frontend?
Currently using template toolkit, so do i keep using it and embed vue or build a standalone vue app, in which case how do i serve it.
There is currently a baclend/frontend and both use template toolkit, i am only planning on reworking the frontend for now so there needs to be some backwards compatability with the rest of the project
submitted by /u/Mowntain-Goat8414
[link] [comments]
- "Have the appropriate amount of fun."
- "construed as a feature"
- "It does what you want, unless you want consistency."
- "'functional' is not to be construed as an antonym of 'dysfunctional'"
- "leaning toothpick syndrome"
I read it at the formative age of 16.
submitted by /u/Kodiologist
[link] [comments]
How does the following work, specifically the triple equal sign print "hello" =~ y===c # -> 4
submitted by /u/Both_Confidence_4147
[link] [comments]
Hey friends, a few weeks back we introduced SlapbirdAPM (an open-source Perl application performance monitor), and received some great feedback from the community! Today we'd like to announce that you are now able to track DBI queries in your applications (only available for Dancer2 and Mojolicious for now), regardless of your database, ORM, etc. Here's what it looks like! You can see the dancer2 code that generated these queries here. preview.redd.it/l2jvz1bne8nd1.… This is just one of the many monitoring features provided by SlapbirdAPM, hopefully you find them as useful as we do! And a reminder we have a *forever* free tier available for everyone! submitted by /u/ivan_linux |
Since the language formerly known as Perl 6 has officially gone off on its own, has there been any effort to implement a true Perl 5 successor?
In my opinion, Raku tried to do too much with the syntax itself, scaled Perl's flexibility to infinity, and made itself unusable.
Perl 5 does not need much for it to become a "modern" language. Instead of extending the flexibility of the syntax, the direction for Perl 6 should emphasize standardizing core utilities to facilitate integration with modern workflows.
- Package/module management and import/export could benefit from streamlining
- Stronger LSP and debug/error tooling (Rust has spoiled me)
- "Prettier" auto-formatting for source code (For those 30yo system scripts, you know the ones I mean)
What would be on your wishlist?
submitted by /u/J_Stach
[link] [comments]
Mo utilities for email.
Changes for 0.02 - 2024-04-26T23:02:53+02:00
- Add tests for error parameters.
- Rewrite the tests so that the functional tests are first and then the errors.